Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
||
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
When attempting loose page (or imposed) proof output to certain output devices, the process occasionally fails with a vague "Failed to initialize printer" error, but at other times it works ok. If you check the diagnostic log on the node where the JTP was running, you will see a message like this: E 08Dec99 18:45:03.718 [355.359] ALPHA2RY1-1 Araxi PPSOutputE OENG_CAraxiOutputEngine.cpp(288): PFWK_proofengine.cpp 1107: CreateDC failed GetLastError:1797 This error is ERROR_UNKNOWN_PRINTER_DRIVER: The printer driver is unknown. |
|
|
|
||
Cause |
If there are multiple proofing JTPs configured in a pool, the output process may get scheduled to use different JTPs at different times, in order to distribute the load. If the process happens to be scheduled to execute on a particular node, and the printer driver for the particular output device type is not correctly installed on that node, the output will fail. |
|
|
|
||
Solution |
Ensure that all nodes have the correct printer drivers installed for every kind of proofing device. Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
proofing |
|
|
|
||
Technical contact(s) |
Rob Prior |
|
Submitted by |
||
Date submitted |
||