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 |
2.2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
Z 29Apr04 22:53:31.843 [3700.4268] YCS862-399 ARAXI PTaskD.XCON_Callback TAKS_JobSub.cpp(1435): Proof2OnYCS863-399:printing(1658): ICC profile not found: D:\Prinergy2.0.4\CreoAraxi\data\ICC-Profiles\G:\Jobs\000_ColorProfiles\swop_press_profile.icc. |
|
|
|
||
Symptoms |
Outputting proofs or plates fail with an error indicating that the ICC profile cannot be found. The path of the ICC profile shown in the error message may also be invalid, in that it contains a drive letter in the middle of the path. The process plan points to an ICC profile that is not in the default location, that is, the %AraxiHome%\CreoAraxi\Data\ICC-Profile folder or the ICC profile is not one of the default profiles. |
|
|
|
||
Cause |
If a relative path is used for the ICC profile, the ICC profile must exist on the primary server and all the secondary servers and render stations that contain JTPs that would use the ICC profiles. If an absolute path is used (whether local or UNC), and the ICC profiles are on the primary server, the ICC profile path is converted to a local path. If the JTP is on a secondary server or render station, the JTP fails to find the ICC profile because it's using the local path instead of a UNC path. |
|
|
|
||
Solution |
Copy the ICC profiles to each Prinergy server in the %AraxiHome%\CreoAraxi\Data\ICC-Profiles folder and use a relative path in the process plan. Note: The ICC profiles must be copied to each Prinergy server whenever any of the ICC profiles are changed or added. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
color, output |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
04 May 2004 |
|