![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
Diagserver.cmd crashes repeatedly, as indicated by error messages in Prinergy Administrator. |
|
|
|
||
Cause |
There are 3 possible known causes: 1.) The directory %ARAXIHOME%\CreoAraxi\system\log is missing. 2.) Sometimes when Araxi is shut down it doesn't let either DIAG_Server.exe or diagserver.cmd clean up gracefully, and sometimes the socket doesn't get closed properly and is left hanging even if the process has completely disappeared. So if you try to restart Araxi or just DIAG by itself, the server will refuse to start up because the socket it needs to bind to already exists. 3.) Even though everything else has been shutdown,either the DIAG_Server.exe or python.exe process is still running. |
|
|
|
||
Solution |
If cause #1: Manually create the directory %ARAXIHOME%\CreoAraxi\system\log If cause #2: - Wait for an unknown amount of time for it to go away by itself, or - Go around and hunt down any clients on the network that might be connected to it from who knows where, or - Reboot to get rid of the socket If cause #3: Get rid of these dangling processes (e.g. using Task Manager) Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
administrator, networking |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||