We have a new Konica Minolta C14000, running Fiery command WorkStation Package version 220.127.116.118, with some virtual printers set up for receiving jobs.
On the server we are running Xerox FreeFlow Core Version: 5.4.1 Build: 22923.
The printer has been added using port 8010 (JDF), and seeing consumable status, virtual printers, and submitting jobs seems to work great in Core.
However, all submitted jobs (for that printer) that show up under "Completed" in the FreeFlow Core web interface gets the status "Cancelled" and the interface freezes for at least 7 seconds PER JOB shown in the list. That means that if we have 10 completed jobs FreeFlow Core hangs for well over a minute just to open the list of jobs. Manually deleting those jobs makes it responsive again.
The workflows are mostly super simple.
Screenshots (not really much to show):
Anything we can do to avoid this? It makes FreeFlow Core an absolute pain to use at the moment.
The Konica Minolta C14000 is not supported by FFCore. You could try updating the EFI. You could also try upgrading FFCore to 5.4.2 -- although I know of no reason that would help.
I assume that the FFCore submitted jobs are successfully printing. My best guess for the erroneous "Cancelled" message is due to the EFI is not providing the correct JDF information to FFCore. I do not have a reason for the 7 second hang on the FFCore GUI.
We have been able to recreate the 7 second problem on the EFI/KM C3070 which FreeFlow Core supports. A BUG has been written. The fix will be in a future release and hopefully addresses the problem on your KM.
We tried as a workaround to send the jobs to a Xerox printer after the KM-printer, as only the last printer shows up in Completed.
Now, we get jobs that hangs with "Pending Submission to Destination". It cannot be deleted. When I press cancel the I get the mesaage: Job XXXXX is in PausedAtPrinter and cannot be cancelled. Jobs sent after it also hangs in the same way (on all workflows).
Core then starts to hang more and more, and becomes unusable. Reboot is required. Then we can delete the jobs, but the problem repeats itself.
Any ideas how to make this work until a new update comes with the bugfix?
Sorry, seems core freezing up was unrelated to this previous bug. It was freezing due to a Xerox machine (1000) for some reason. So a separate bug. Ignore that last bit then.
But tips for better workarounds to the 7-second hang bug is still appreciated.
David: Any rough idea when a fix might be expected? I notice there has been two new versions (5.4.2 and 3) but I didn't see anything in the changelog.