Product

Platform

Operating system

Error

Symptoms

At startup after a clean install, an error message appears in Prinergy Administrator saying that diagserver.cmd has crashed. Diagserver runs fine after it's restarted by the Araxi service.

Cause

Diagserver.cmd has a delay to wait for PDiagnosticD.exe to create the first log file, but sometimes PDiagnosticD.exe takes longer than expected and diagserver.cmd dies after it fails to find the log file.

Diagserver.cmd is responsible for feeding the log file to diag viewer clients (such as DiagView.exe)

Solution

The problem should normally be self-correcting. The first time the system is started on a freshly installed system, it might fail initially, but usually the Araxi service should automatically restart it, and then it should be okay after that.

If this doesn't happen, try the following workaround:

In %ARAXIHOME%\CreoAraxi\system\log, create a dummy empty file. A sample filename is Araxi000.log.

Better still, whenever there are flaky problems with DIAG, stop Prinergy, and try to run just diagserver.cmd by itself in a console window (diagserver.cmd -d 2) to get extra debug info. If this runs without reporting any red error messages, then it can be stopped by executing "diagserver.cmd stop" in a different console window. Then restart the Araxi service normally.

Permanent fix:

See also

Keywords

administrator, networking

Technical contact(s)

Simon Chen

Submitted by

Date submitted