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 Satellite | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
E 23Jan03 16:28:04.075-PST [1636.1832] YCC9999-999 AraxiLab PCreateJacketOnStart.main CORB_NameService.cpp(116): unable to resolve Name Service System exception `TRANSIENT' Locality: exception has been received "over the wire" Completed: no Minor code: 0x0 |
|
|
|
||
Symptoms |
If Prinergy is started, the majority of the processes will start then immediately stop. Eventually, the Implementation Repository will stop and after that, all remaining processes will stop. |
|
|
|
||
Cause |
The Orbacus configuration is incorrectly configured or has been corrupted. This may be the result of changing the computer name. | |
|
|
||
Solution |
Run the OrbacusConfig script to re-configure Orbacus. A link to the OrbacusConfig.cmd script can be found in the See Also section of this workaround. To run OrbacusConfig.cmd: 1) Open a command prompt window 2) Enter: ORBACUSCONFIG -init Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
daemon, orbix |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
23 Jan 2003 |
|