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.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
After upgrading to Prinergy 2.0.7, any job that was created before 2.0.7 will not show the online/offline status for the job in workshop. |
|
|
|
||
Cause |
In Prinergy 2.0.7, the online/offline status of the job is kept in the database. Prior to 2.0.7, the status was determined dynamically by checking the job volume for the existence of the job folder. In many cases, checking the job volume was time consuming, thus, a change was made to record the status of the job in the database. The job status is changed when the job is created, retrieved from archive or purged. | |
|
|
||
Solution |
A Python script was written which will update the database with the online/offline status of each job. The script will check the job volume and if it detects the existence of the job folder and the two sub-folders 'System' and 'UserDefinedFolders', it will assume the job is still residing within the job volume and will update the database with the correct status. This utility should only be used by a Customer Service Representative or the Response Center. To run the script, do the following: 1) Copy the script to the server 2) Open a command prompt window 3) Run the script with the --noupdate switch: * D:\> FixOnlineStatus prinergy/araxi@araxidbserver --noupdate 4) If the results look OK, then run the script without the --noupdate switch to update the database with the status: * D:\> FixOnlineStatus prinergy/araxi@araxidbserver 5) The FixOnlineStatus.cmd script will create a log file called FixOnlineStatus.log. It is recommended that you save this log file in case you wish to identify if the script was used to change the status for a particular job. * * EXAMPLE: * * Perform a check with the --noupdate switch first: * * D:\> FixOnlineStatus prinergy/araxi@araxidbserver --noupdate * Running in NOUPDATE mode. No changes will be made to the database. * Connecting to database using prinergy/araxi@araxidbserver... * Connected! * * Job name Status * ------------------------------------------------------------ * HDPP - hill1 ONLINE * TEMPTEST_csaustralia ONLINE * * * Now update the database: * * D:\>FixOnlineStatus prinergy/araxi@araxidbserver * Connecting to database using prinergy/araxi@araxidbserver... * Connected! * * Job name Status * ------------------------------------------------------------ * HDPP - hill1 ONLINE * TEMPTEST_csaustralia ONLINE Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
job manager or job folders, workshop |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
Dec 6/01 |
|