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 |
AraxiSysStateBackup service on the secondary server fails to restart. |
|
|
|
||
Cause |
May be caused by the scripts attempting to start the service before it has completely stopped. The next time backup runs, the AraxiSysState service will start since it was stopped by the previous backup. This will result in the remote SysState backup failing every other time backup runs. |
|
|
|
||
Solution |
Insert a pause (time.sleep(5)) between the stop and start commands in the AraxiSecondaryBackup.py file in the Primary server. ... ... if (AraxiUtil.Ping(node) == TRUE): backupService.StopService(backupServiceName, node) time.sleep(5) <==== ADD THIS LINE backupService.StartService(backupServiceName, node) Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
||
Date submitted |
||