Printing issues are often a bit challenging to troubleshoot. I don’t see anything obviously wrong with your setup, but I almost never print reports.
Does your report print okay when you test it in the Schedule panel in the reporting workspace? Does it save okay if you change the distribute action to ‘save’ and give it a path/filename relative to the gateway?
Is there anything in the gateway logs? Try turning the reporting.Data log to debug to get the most info.
i see a job in the queue but print a white label?
Is the problem that is not processed from the printer driver ? There’s another system for print directly ?
Without turning your logs to trace, it’s going to be hard for you to debug further. Your best bet is to contact support and have them help you with this.
It’s going to depend on where you think the problem might be, but I’d start with reporting.Scripting. If that doesn’t do it, try turning all of reporting to trace and use the MDC keys for your report name and your project name to find the log statements for that report.
That’s a Python (and many other languages) thing, to clarify, not an Ignition thing - backslashes are a common ‘escape’ character, so if you need to represent a literal newline, say, in a string, you use "\n", since there’s no “character” that can represent a newline. The escape character for the backslash itself is…two back slashes - so "\\" is actually defining a single character \ in the output. You can prefix the Python string literal with r to make it “raw”, meaning it won’t process escape characters: sPath = r"\\vmware-host\Shared Folders\etc"
Or, you can “double” the escape characters to make the same output string: sPath = "\\\\vmware-host\\Shared Folders\\etc"