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 |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
||
|
|
||
Symptoms |
The AraxiBackup.log file shows that the system backup has failed with a message indicating that the AraxiSysStateBackup service could not be started on the primary server. |
|
|
|
||
Cause |
The AraxiSysStateBackup service only exists on secondary servers. The backup script thinks the the primary server is a secondary server. The list of the secondary servers to be backed up is defined by the registry key: HKLM\Software\Creo\Araxi\2.0.4.BLD69\Default\System\Backup\SecondaryNodeList. The primary server is normally not in this list. | |
|
|
||
Solution |
Remove the primary server name from the registry: HKLM\Software\Creo\Araxi\2.0.4.BLD69\Default\System\Backup\SecondaryNodeList. Note: The server names are separated by semi-colons. When removing the primary server from the list, remove the extra semi-colon (if any) as well. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
28 Aug 2001 |
|