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 |
System backup fails with the error: Error: The AraxiVolume_<server name>_<drive letter> well known share could not be converted to a local path. The backup completes but the completion time is not updated in UADM. |
|
|
|
||
Cause |
The backup script is looking for the local path of the AraxiVolume share in the LanmanServer\Shares registry key. A typical share will contain these values: CSCFlags=0 MaxUses=4294967295 Path=J:\ Permissions=63 Type=0 If the registry is missing the CSCFlags=0 entry, the backup script will fail to get the Path entry. |
|
|
|
||
Solution |
Add the entry CSCFlags=0 for all for the AraxiVolume share(s) in the LanmanServer\Shares registry key. 1) Start REGEDT32 2) Navigate to HKLM\System\CurrentControlSet\Services\LanmanServer\Shares. 3) Double-click each AraxiVolume share found in the registry key and add the CSCFlags=0 at the top of the list. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
12 Apr 2002 |
|