Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Registry corruption causes Prinergy and W2K to behave unexpectedly


Product

  Prinergy Connect 2.0

Platform

 

Operating system

 


Error

 


Symptoms

 

The symptoms vary, depending on the registry key that has been corrupted, and can include:

1. JTP's fail to start.

2. Printer control panel does not open.

3. "net share" from the command line hangs in the middle enumerating shares.

4. Diag view daemon and Locator daemon continually crash on startup.

5. NTBackup or Archiver fails with an error from the RSM indicating that it is not able to read the xxxMLL.dll.

In some cases, Regedt32 will not be able to read the registry values, but when using Regedit, it works ok.

Registry keys that have been found to be corrupt:

HKLM\System\CurrentControlSet\Control\Session Manager\Environment

HKLM\System\CurrentControlSet\Control\Session Manager\SubSystems

HKLM\System\CurrentControlSet\Control\NTMS\OMID\Tape

HKLM\System\CurrentControlset\Services\LanmanServer\shares

HKLM\Software\Microsoft\Windows NT\Current Version\Print\Printers


Cause

  Microsoft has confirmed that booting the OS using the "last known good" option causes registry corruption. Please avoid using this option.

A fix is scheduled for W2K service pack 3. This will prevent the registry corruption, but will not fix keys that are already corrupt.


Solution

 

To correct the problem:

1. Restore the system state from a know good backup

or

2. Export the key using Regedit. Delete the affected key and import the exported file.

Permanent fix:


See also

 


Keywords

 

registry, Windows 2000


Technical contact(s)
 

Simon Chen

Submitted by
 

Simon Chen

Date submitted
 

19 Mar 2002


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.