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 |
Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
A job is homed on a Unix server and you are using Hummingbird NFS to access the Unix server. The job is renamed, and now you cannot open the pdf file using Workshop. The error message in Workshop indicates that the path to the pdf file is pointing to the old job folder. |
|
|
|
||
Cause |
The Default Filename Case setting for Hummingbird NFS is incorrect. In Control Panel -> Network and Dial-up Connections -> Local Area Connection -> Properties -> Hummingbird NFS Maestro Client, the Default Filename Case is set to either Lowercase or Uppercase. It should be set to Preserve Case. Prinergy will store the relative path for the file in the database if the file is within the job folder. If the Hummingbird NFS is set to convert all filenames to lower case, the job folder will be created in lower case letters, however, Prinergy stores the folder path in the original case. Prinergy performs a case-sensitive comparison of the path to the file to the path of the job folder. If the comparision fails, Prinergy will store the absolute path for the file instead of the relative path. When you rename the job, the file will retain the original path because the absolute path was recorded in the database. |
|
|
|
||
Solution |
Change the setting for Hummingbird NFS. 1) In Control Panel -> Network and Dial-up Connections -> Local Area Connection -> Properties -> Hummingbird NFS Maestro Client, change the the Default Filename Case is set to "Preserve Case". 2) Disconnect the Hummingbird NFS network drive and reconnect the network drive in . All jobs created with the incorrect Hummingbird NFS setting will not rename properly because the the database will contain absolute paths for the files. To resolve this problem follow these steps: 1) Correct the Hummingbird NFS setting (see above) 2) Rename the job to some other name 3) Rename the job back to the original name using all lower case letters if the Hummingbird NFS setting was set to Lowercase, or rename the job using all upper case letters, if the Hummingbird NFS setting was set to Uppercase. 4) Rename the job to the new desired name. All registered files contained in the job folder will now be recorded in the database using the relative paths. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
Unix |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
17 Jun 2002 |
|