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 |
UADM (Prinergy Administrator) does not show the status of the current backup. |
|
|
|
||
Cause |
The HKLM\System\CurrentControlSet\Services\LanmanServer\Shares registry key contains an entry that does not point to a valid folder. The backup script is attempting to write log files to a folder on the first AraxiVolume share it finds in the registry. If the first AraxiVolume share does not point to a valid drive or folder, the backup script will fail. This 'phantom' share can occur if the drive is removed from the system before deleting any NT shares on that drive. |
|
|
|
||
Solution |
Remove the phantom share from the system from the HKLM\System\CurrentControlSet\Services\LanmanServer\Shares registry key using Regedt32. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
Feb 14/02 |
|