![]()
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 |
Wed Oct 10 16:26:02 2001 *** Error: Cannot open or create pool: Backup\Prinergy. Wed Oct 10 16:26:02 2001 Wed Oct 10 16:26:02 2001 *** Explanation: The system backup tried to initialize the Backup\Prinergy pool before Wed Oct 10 16:26:02 2001 using it and could not. Wed Oct 10 16:26:02 2001 Wed Oct 10 16:26:02 2001 *** Solution: This error usually occurs when the account running the AraxiBackupManager Wed Oct 10 16:26:02 2001 service does not have administrator privileges. Wed Oct 10 16:26:02 2001 |
|
|
|
||
Symptoms |
System Backup fails and the AraxiSystemBackup.log file contains an error message indicating that the Backup/Prinergy pool could not be opened or created. |
|
|
|
||
Cause |
The RSM contains another pool that starts with the word Backup. For example, there may be another pool called BackupWeek. The backup script will mistakenly attempt to open the BackupWeek pool instead of the Backup pool. However, the GUID used to open the BackupWeek pool is invalid. | |
|
|
||
Solution |
Rename the pool with the similar name to something else. For example, change BackupWeek to BackWeek or WeekBackup. Do not use the word Backup as the first part of the pool name. NOTE: If customer is running BackupExec v8, it will create a media pool \BackupExec\DLT when it starts and we cannot rename the media pool. In this case, we advise not to run backupexec on the system that running Prinergy Backup. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
backup |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
10 Oct 2001 |
|