Product

Platform

Intel

Operating system

Windows 2000

Error

Symptoms

When starting Prinergy, the Diagnostic View and Locator daemons crash.

UADM shows Prinergy is running, but the only Prinergy processes displayed in UADM are:

- Corba Monitor daemon (running),

- Diagnostic View daemon (crashed),

- Disk Monitor daemon (running),

- License Key Monitor daemon (running),

- Locator daemon (crashed).

If you start the Araxi service using another user account, the results are the same.

If you start Araxi from the command line, all the processes start properly.

Cause

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

If you view the registry key in REGEDT32, no values will be displayed, but if you view the registry key in REGEDIT, all the values will be displayed.

The processes are failing to start or are crashing because NT is failing to read the Environment registry key and the Path environment variable is not being passed to the process.

This corruption may occur after someone has booted the system from the Last Known Good configuration. There is a bug in Windows 2000 where the Last Known Good registry hive is corrupted whenever it is updated. This bug has been fixed in Win2K SP3. See the Microsoft Knowledge Base article: Q307308.

Solution

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.

Permanent fix:

See also

Keywords

daemon, diagview

Technical contact(s)

Stan Yoshida

Submitted by

Stan Yoshida

Date submitted

Jan 25/02