We get random but consistent errors on jobs that run fine 99% of the time. What are the troubleshooting steps or configuration / environmental factors I need to check for errors like this:
DEBUG: 09:45:07.269 Starting plugin Create Output - 9:45:07 AM
DEBUG: 09:45:07.273 Using cached config file (id = 24012175).
DEBUG: 09:45:07.273 Starting output creation operation…
WARN : 09:45:07.668 Cached version not available, attempting to upload file.
DEBUG: 09:45:07.698 Starting output creation operation…
ERROR: 09:45:07.887
W3001 : Error while executing plugin:
HTTP/1.1 500 Internal Server Error LoggedApplicationException:
There was an error running the output creation process caused by ApplicationException:
Output directory 'C:\Users\pdsupport_pc\Connect\filestore\output.6383907864630742270\12165-0
Looks like you are using variables in the Output Preset to set the names of the output files and one of these variables gets expanded to an incorrect value. The "
In the more general sense, the fact that the error gets reported in Workflow doesn’t necessarily mean that this is where it actually occurs.
For example, here the error is in the Create Output plugin and is typed as an Internal Server Error. This means that the error actually occurs in Connect Server, not in Connect Workflow. So you have to chase the error data from the Server logs rather than Workflow’s. And there you may find that, in turn, Server returns an error that has actually occurred in the Weaver Engine, the specialized helper program that handles the production of the final print output.
So there is a bit of cat and mouse chasing to do. But usually, once the pieces are put together (and there are rarely more than 2 or 3), the answer is obvious to those skilled in the arts.
Here, as Phil mentioned, there seems to be funky with the configuration of the output filename as it contains a piece of HTML including a smaller then character, which is illegal in file names.
Thank you, this is precisely the information I’m looking for. Not the specific error case itself, but how to use that error and the logs to help track issues down. I don’t like going to Support for every little thing that happens.
You may find that log viewing software, such as LogViewPlus that we use internally, can help immensely in that matter. Sadly, while it does wonders for Design, Server, and al., it reacts a bit poorly to the logs from Workflow. But we’ll be working on that.
