![]()
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 |
The system backup backs up the system correctly, but at the end of the backups, this message appears in the AraxiSystemBackup.log file: '*** Error: The AraxiVolume_<server name>_<drive letter> well known share could not be converted to a local path.' |
|
|
|
||
Cause |
The system backup script is looking for an AraxiVolume share on the primary server to store a backup copy of the AraxiSystemBackup.log file. This backup copy of the log file can be used to determine which tape was last used for the system backup in the event of a system drive failure. If all log files are missing, the only way to determine which tape was used for the last backup would be to mount each tape and catalog them. The backup script will report this error if there is no AraxiVolume share on the primary server or if there is an AraxiVolume registry entry in HKLM\System\CurrentControlSet\Services\LanmanServer\Shares for a drive that is not physically attached to the system. |
|
|
|
||
Solution |
Create an AraxiVolume share on the server, it should be on the RAID drive or another drive other than the system drive. For example, if the have a J: drive place it there, if there is no J: drive you can use the E: drive, however, note that on some systems the E: drive is a partition on the same physical disk as the system (D:) drive. NOTE: Do not add this AraxiVolume share in UADM to the list of shared volumes accessible by Prinergy. If there is an AraxiVolume entry in the registry for a non-existent drive, remove the AraxiVolume entry. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
11 Oct 2001 |
|