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 ; Prinergy Direct 2.0 Level 2.0.7.4; Prinergy Access 2.0 Level 2.0.7.4; Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; Prinergy Powerpack 2.1 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
Orbacus name service not updated in registry <machine name> Fatal error! Unable to update registry on <machine name> |
|
|
|
||
Symptoms |
When failing over an EPM (Emergency Plate Making) server, you get the following error messages: Orbacus name service not updated in registry <machine name and then Fatal error! Unable to update registry on <machine name> This may happen repeatedly if there are several Secondary servers. This problem does not occur during normal operation. |
|
|
|
||
Cause |
This problem occurs if new Secondary servers are added to an existing Prinergy system, when those new Secondaries were built and installed in Production. What normally happens is that the registry on the Secondary machines is updated to reflect the new Primary server (the existing one on site). This change is missed in one location, which doesn't affect anything until you try to do an EPM failover: HKLM\Software\OOC\Properties\ooc\orb\service Value=Nameservice The value of Nameservice will probably be corbaloc::prime21:49101/ (etc...) |
|
|
|
||
Solution |
Change the value of Nameservice to corbaloc::primary-server-name:49101/ (etc...) Leave the rest of the value as-is! Change only the server name! This procedure may need to be repeated on any Secondaries at the site that were built in Production and then added to the existing Prinergy system. Again, this problem does not affect day-to-day use, it only happens when you try to do an EPM failover (including Rushmore, which is built upon EPM). Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
Database Reports, EPM, Emergency Platemaking (EPM), Hot Standby, orbix, registry |
|
|
|
||
Technical contact(s) |
Robyn Lundstrom |
|
Submitted by |
Robyn Lundstrom |
|
Date submitted |
21 Jul 2003 |
|