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 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
06-Dec-2002 00:46:09 ERROR: Cause: exceptions.Exception Error: Failed to backup Orbacus configuration files. Details: exceptions.Exception File D:\Prinergy2.0.4\IonaOrbacus\bin\Names.Db does not exist. 06-Dec-2002 00:46:10 TRACEBACK: Exception in process 2436, thread 1568 Traceback (innermost last): File "E:\Temp\~ppu.0\ppuinstall.py", line 499, in InstallPatch PPUScript.install( self ) File "E:\Temp\~ppu.0\PPUScript.py", line 336, in install None File "E:\Temp\~ppu.0\PPUScript.py", line 1124, in MiscPostFileCopyStep None File "E:\Temp\~ppu.0\PPUScript.py", line 4320, in MiscPostFileCopyStepTo210 None File "E:\Temp\~ppu.0\PPUScript.py", line 2217, in ConfigureOrbacus None File "E:\Temp\~ppu.0\PPUScript.py", line 2869, in BackupOrbacusConfiguration None Exception: Error: Failed to backup Orbacus configuration files. Details: exceptions.Exception File D:\Prinergy2.0.4\IonaOrbacus\bin\Names.Db does not exist. |
|
|
|
||
Symptoms |
The 2.1.0.0 Major Update fails while configuring Orbacus with the error below. |
|
|
|
||
Cause |
The IMR is trying to start the Corba server called NameService but the NameService is failing to start. The NameService server creates the Names.db file, but since it fails to start, the Names.db is not created. * * The reason the NameService is failing to start: The Rundir parameter for the Corba server is by default set to NULL by the 2.1.0.0 Major Updater. If the Rundir parameter is null, the IMR will try to start the NameService process using the C: drive. If the system does not have a C: drive, the NameService process (Nameserv.exe) cannot be started. |
|
|
|
||
Solution |
Ensure the system has a C: drive. Normally, systems shipped from Production will have a C: partition of 30 MB - 2 GB which contains the system boot files (ntldr, io.sys, msdos.sys etc.). If the system does not have a C: drive, create a partition and assign the drive letter C:, or change the drive with the boot files to C: . (Do not change the system drive with the WINNT folder to C: !) If you change the drive letter of the boot drive, run REGEDIT and search for any occurrences of the old drive letter and change them to C:. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
install |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
11 Dec 2002 |
|