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


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


Diag View daemon and PDiskMonD crashes, then Araxi service stops by itself


Product

  Prinergy Connect 2.0

Platform

 

Intel

Operating system

 

Windows 2000


Error

 


Symptoms

 

1) The Diagnostic View daemon and the Disk Monitor daemon (PDiskMonD) crashes when Prinergy is started. Prinergy will then shut down by itself.

2) The contents of the registry key HKLM\System\CurrentControlSet\Control\Session Manager\Environment when viewed using REGEDT32 appears to be empty.


Cause

  The registry may be corrupted. This can occur from either a blue screen crash or from booting a Win2K pre-SP3 system from the Last Known Good.

There is a bug in Win2K (all versions up to SP2) which results in the Last Known Good registry hive getting corrupted whenever the Last Known Good hive is updated. If you boot the system from the Last Known Good, the CurrentControlSet hive will contain all the corrupted keys.

The Diagnostic view daemon and Disk Monitor daemons crash because the HKLM\System\CurrentControlSet\Control\Session Manager\Environment registry key is corrupted.


Solution

 

You can repair the Environment registry key, however, it may be better to restore the entire System State from tape if the system was booted from the Last Known Good, since there may be hundreds of registry keys that are now corrupt.

There are two ways to repair the Environment registry key:

1) In Control Panel | System | Advanced, open Environment Variables.

2) In the User variables section, click on Edit, however do not change the value. Just click OK.

3) Click OK again to exit the Environment Variables dialog box. This will re-write the entire Environment registry key and clear out the corruption.

4) Re-start Prinergy.

Or (This method will allow you to repair any registry key that is found to be corrupt):

1) Start REGEDIT (not REGEDT32)

2) Go to the HKLM\System\CurrentControlSet\Control\Session Manager\Environment key

3) Right-click the Environment key and rename it to something else. e.g. Environment1

4) Right-click the key and rename it back to Environment. The renaming will rewrite the entire key.

The better method is to restore the system state from a known good backup. If this is a secondary server, the system state backup is kept in the TEMP drive in the AraxiBackup folder (e.g. E:\AraxiBackup\SysStateBackup.bkf).

To restore a primary server, see the Prinergy 2.0 Backup Guide (03-4171B-D-PM01) for details.

To restore the system state on a secondary server:

1) Start NTBackup (Start -> Run -> NTBACKUP)

2) In the Restore tab, select Original Location for the Restore File To: drop down box.

3) In the left pane there should be an entry called File, right-click it and select 'Catalog file...'

4) Browse to the location of the SysStateBackup.bkf file on the TEMP drive.

5) Select the SysStateBackup.bkf file and click OK twice.

6) Click on the + next to File to expand it.

7) Click on the + next to the System State backup set, another dialog box to catalog the backup may appear, click OK to perform the catalog.

8) Click on the checkbox next to the System State entry.

9) Click on the Start Restore button.

10) Restart the server. NOTE: It may take several minutes for the server to shut down, allow it to shut down and restart on it's own.

Permanent fix:


See also

 


Keywords

 

daemon, diagview


Technical contact(s)
 

Stan Yoshida

Submitted by
 

Stan Yoshida

Date submitted
 

15 Oct 2001


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