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
Third Party Workflow Unable to Connect to Print Console 1.0 |
|---|
Applies to |
Systems that have installed Print Console v1.0.4 (either the patch files or a full install from the Production CD) and connect directly to a third-party workflow/RIP via CRI (i.e. Rampage, Delta). |
Problem |
Third-party workflow that connects directly to Print Console via a CRI cannot connect after loading Print Console 1.0.4. |
Background |
Print Console 1.0.4 (the current shipping version of Print Console 1.0) uses the tiffdownloader.exe that was created for Print Console 2.0. This file uses a driver called “ctprip.dll” to check the registry for a valid CRI License Key is in the registry. Since it was designed for use with Print Console 2.0, it looks for the CRI License Key based on the registry structure of v2.0, not v1.x. When it can't find the License Key, it does not allow the third party to connect. The patch referred to below moves the License Key from... HKEY_LOCAL_MACHINE/SOFTWARE/Creo/PrintConsole/v1.0/Allegro /CtpwsConfig to... HKEY_LOCAL_MACHINE/SOFTWARE/Creo/PrintConsole/v2.0/System Config/CRILicenseKey. |
Workaround |
No workaround availabe.
|
Permanent Fix |
Enter a valid CRI License Key in the Print Console GUI and then apply the CRI Licence Key patch from the Print Console Downloads page. |
Technical contacts |
Jose Delgado, x2319 |
Date submitted |
July 31, 2000 |
Last modified |
July 31, 2000 |
Tested 
Not Tested