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 |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
D:\rehost>pchangejobshare PRINERGYSTORAGE AraxiVolume_PrinergyStorage_G -h YCS845-390 -s AraxiVolume_ycs845-390_J Making sure the system is shut down... Initializing database access... Checking for conflicts before updating from '\\YCS845-390\AraxiVolume_ycs845-390_J' to '\\PRINERGYSTORAGE\AraxiVolume_PrinergyStorage_G' \\PRINERGYSTORAGE\AraxiVolume_PrinergyStorage_G\Jobs\06818-03\System\ImpositionPlans\2003 8 8pg 12-13_1.pdf will conflict with a file being moved from \\YCS845-390\AraxiVolume_ycs845-390_J |
|
|
|
||
Symptoms |
You are moving jobs from one AraxiVolume to another volume that already contains jobs. When you run PChangeJobShare, it reports that a file that could not be moved due to a conflict. |
|
|
|
||
Cause |
A file with the same name and path exists on both the source and destination volumes. These two files may potentially contain different content, thus you cannot substitute one for the other. PChangeJobShare will not let you move the jobs onto the other volume until the conflict is resolved. The conflict could be a pdf subpage, a font search path or an image search path. |
|
|
|
||
Solution |
To resolve a conflict: 1) Identify all the conflicting files. - In Prinergy 2.2 and up, stop Prinergy and run PChangeJobShare with the -a option. (or use the script CheckConflicts.cmd) - e.g. PChangeJobShare <to_server> <to_share> -h <from_server> -s <from_share> -a - In Prinerg 2.1 and below, PChangeJobShare does not have the option to display conflicts. Use the script CheckConflicts.cmd. You do not have to shut down Prinergy to run the script. - e.g. CheckConflicts.cmd <to_server> <to_share> <from_server> <from_share> 2) Identify which jobs contain the conflicting files. The script CheckConflicts.cmd will display all the jobs that are using the conflicting file(s). - e.g. CheckConflicts.cmd <to_server> <to_share> <from_server> <from_share> 3) Remove the conflicting file(s). If the conflicting file is used as input for a job, remove the input file. If the conflict is an image or font search path, remove the search path. ** Do not remove the pdf subpage itself, the conflict is usually caused by another job using the subpage as input. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
30 Sep 2004 |
|