Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
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 |
When you start the Araxi service (e.g. using UADM), all you see is three rows, one for each of the daemons directly started by the Araxi service. As daemons start up, the bottom row shows them getting launched. This row keeps getting overwritten as new ones are started, but the window does not fill up with the entire list of daemons in the expected manner. No errors or warnings appear in UADM, the NT Event Log, or Diagnostic log. A round-about clue is to use REGEDT32.EXE to try to access the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib If this key is grayed out (inaccessible), Prinergy will not work. |
|
|
|
||
Cause |
After stopping and restarting Prinergy a number of times, eventually some essential system resource becomes sufficiently depleted that the Araxi service is no longer able to query the list of running daemons. If you run Araxi.exe with the -c option to connect to the running Araxi service, and type the command 'status', you will see repeated messages saying "WARNING: failed to get a list of running processes." This message is never forwarded to places where end users are likely to see them. What it really means is that the registry key HKLM\Software\Microsoft\Windows NT\CurrentVersion\Perflib is not accessible due to severe system resource depletion. This key is needed by the Araxi service to query performance counters, in order to detect if processes are running or not. |
|
|
|
||
Solution |
Reboot the system. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
administrator, daemon, networking |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||