Your Forum post was sent to my e-mail (not sure why) and not posted here is the post:
Yep, submission status is OK and printer status is Normal.
It's a Xerox Colour 1000, with a FreeFlow 9.0 rip. It was fine when I went to look at it yesterday (no error messages, and prints fine), and I've restarted it just in case, but FreeFlow Core would still start hanging. Even if FreeFlow Core had problems communicating with the rip/printer I don't think it should freeze up to the point where it requires a server reboot.
Anyway, we don't know exactly what/when the problem triggers as it has been hard to test.
I just did a test:
Submit two test jobs (through Core) to a simple Workflow that sends jobs to the 1000. Works fine. Submit two test jobs (through Core) to a simple Workflow that sends jobs to our KM-printer (JDF/port 8010). Works fine (except it hangs for 7 seconds per job when checking the Completed jobs tabs – a confirmed bug). Submit two test jobs (through Core) to a simple Workflow that sends to the KM-printer, then the next step in the workflow sends it to the 1000. Works fine.
So... now it is working again... This is so strange... The last couple of days it would mess up Core. Guess we have to avoid touching it and hope it doesn't start again...
Could you contact Xerox customer service? The problem (at least one version of it) concerns a Xerox printer, customer support should pursue the problem. What Xerox printer is it? Is the printer's submission status (seen in the Printer Management GUI) in an "OK" state?
Hm, no, it keeps happening still. One job hangs with "Pending Submission" and Core goes into potato mode and no jobs can be sent through, requiring reboot to cancel the hanging job(s). Been using USB sticks instead today.
Is it because we send the job first to a KM-printer (JDF/port 8010) and then that step in the workflow is immediately followed by sending it to a Xerox-printer (FreeFlow v9)? Have not had enough time to test this properly as we have a lot to do, and I don't have access to the server (requiring me to get hold of a 2nd person to do the reboot).
Need to test doing yet another reboot, removing the Xerox from all the workflows with the KM-printer, then sending jobs directly to the Xerox to see if that also causes hangs (although it has never been an issue before). No chance until tomorrow at the earliest...
Printer status on all printers shows as "Normal".
Forgot to mention, we are already on version 5.4.1.
Seems the license on the Xerox FreeFlow rip (version 9.0 SP3) on that printer expired that day (technician had forgotten to install the new license), causing Core to hang when it attempted to communicate/send jobs to it. The rip software was still open, just not working right, and after restarting it it told us the license had expired the previous day. Installing a new license on FreeFlow made everything work again, and Core no longer hangs when sending jobs to it. Strange, but at least it is "fixed" for now.
Could be the FFCore version you're using. In version 5.4.1 there's a solution for this issue:
• Fixed issue with some jobs being stuck in a pending state when sending jobs to the printer.
So if you are on an earlier version, it's recommended to upgrade...
We have the same problem. Stuck in "Pending Submission to Destination" and tells me it is "PausedAtPrinter" so cannot be cancelled. No way to delete it. It also causes all jobs sent after it to hang with the same status, so nothing can be printed on any printer.
Rebooted the server to clear it.
Then it happens again with a new job. We can't be rebooting the server every few hours as we need to contact IT support for this. Did you find any solution to your issue?
In our case i suspect it is related to JDF-jobs (for a Konica Minolta printer). Core sends the jobs via JDF on port 8010 since it's a non-Xerox destination (we use Fiery in our case). Since this is bugged in the current version and causes FreeFlow Core to freeze for 7 seconds *per job* listed in "Completed Jobs" (with e.g. 20 jobs this means 2+ minutes delay just to open it) we have now as a workaround added a 2nd print destination (a Xerox printer) that it sends the job to (where we regularily delete the jobs) after it has been sent to the KM-printer (since only the last printer shows in Completed Jobs, so we avoid the freeze).
With the "Pending Submission to Destination" error it says the last attempted preset is the Xerox-printer (last step of the workflow). So can't be sure it's the previous print step causing it.
So working around one bug, seems to lead to another. Any suggestions for other workarounds to get Core to behave? I just want it to not freeze up all the time. :/
Rebooting the server should clear the job(s). A call to Xerox service will be necessary if it happens again -- or the job does not clear.
I have add a jobb to FreeFlow core but it is stucked in the status Pending Submission to Destination.
It cannot be deleted. When I press delete it is not deleted and no error/info message is shown.
When I press cancel the I got the mesaage:
Job XXXXX is in PausedAtPrinter and cannot be cancelled.
Any ideas what I need to do?