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.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 ; Prinergy 2.3, 3.0, 3.1 | |
Platform |
||
Operating system |
Windows 2000, SP4 |
|
|
|
||
Error |
A pop-up window appears on the Prinergy servers reporting that the Prinergy-Database replication job is not running. |
|
|
|
||
Symptoms |
After you restart the primary, the Prinergy-Database replication job disappears. |
|
|
|
||
Cause |
The VSR database may be corrupt. | |
|
|
||
Solution |
Create new VSR database files. 1. On the Prinergy primary server, stop the RMS service. 2. Locate the VSR database directory (<DataDrive>:\VSR\Databases). 3. Rename the RXDB and RXDB.index files. 4. Restart the RMS service. This will create new database files. 5. Open the VSR console. 6. Recreate the Prinergy-Database replication job by running the Create&StrtPrinergy-DatabaseJob.cmd script. 7. Monitor the system if the replication job remains intact after restarting the server. Permanent fix: |
|
|
|
||
See also |
http://support.veritas.com/docs/245296 |
|
|
|
||
Keywords |
EPM, Emergency Platemaking (EPM), Hot Standby, administrator, backup |
|
|
|
||
Technical contact(s) |
Philip Samaniego |
|
Submitted by |
Philip Samaniego |
|
Date submitted |
09 Nov 2006 |
|