![]()
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 |
PMainDirectoryD JCKD_JacketRenamer.cpp(248): Renaming jacket with id 00000000000000007118 to 51220 Where PMainDirectoryD JCKD_JacketRenamer.cpp(441): Stopped watching hotfolders for job 00000000000000007118 PMainDirectoryD JCKD_JacketRenamer.cpp(454): Stopped watching hotfolders inside directory \\YCS726-349\AraxiVolume_YCS726-349_J\Jobs\51220 Where Mag PMainDirectoryD JCKD_JacketRenamer.cpp(253): Preparation for rename done. PMainDirectoryD JCKD_JacketRenamer.cpp(261): Job marked in database as being renamed. ... PJobD.main APPL_CorbaServerApplication.cpp(291){2f3a02a32f3a02a32f3a02a32f7bb7b4} : The Araxi Job Server is starting. PJobD.main DBIF_DBManager.cpp(482){2f3a02a32f3a02a32f3a02a32f7bb7b4} : Connected to database; schema version = '87' PJobD.main JCKD_JacketInfoCache.cpp(136){2f3a02a32f3a02a32f3a02a32f7bb7b4} : Unable to refresh the jacket info cache for job00000000000000007118 PJobD.main JCKD_ReadOperationsImpl.cpp(200){2f3a02a32f3a02a32f3a02a32f7bb7b4} : Can't find jacket 00000000000000007118 in database. PJobD JCKD_ZombieFilter.cpp(76){2f3a02a32f3a02a32f3a02a32f7bb7b4} : Job is a zombie. Throwing a NO_IMPLEMENT error workshop com.creo.araxi.USVW.USVW_JobServer$eJobDestroyedError at com.creo.araxi.USVW.USVW_JobServer.HandleSystemException(USVW_JobServer.java:274) at com.creo.araxi.UORB.UORB_ExceptionHandler.HandleSystemException(UORB_ExceptionHandler.java:148) ... |
|
|
|
||
Symptoms |
A job is renamed, but it fails with the error message indicating that the job is a xombie. Workshop then crashes. |
|
|
|
||
Cause |
There is a problem with the job rename feature, where the job folder is locked when the job folder is being renamed. This happens on some systems, and it appears to happen on jobs that have been archived and only if the job is on the primary server. |
|
|
|
||
Solution |
To complete the job rename: 1) Rename the job folder to match the job name shown in Workshop. 2) In Workshop's Job Finder, select the job and click File -> Rename Job... 3) Do not change the job name, just click on Rename. The rename job function will complete. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
workshop |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
05 Dec 2002 |
|