![]()
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 |
Dr. Watson reports Exception: Access violation [0xc0000005], Address 0xc0000078. When viewed from Prinergy Administrator, it reports that Prinergy is stopped. NT Task Manager lists all Prinergy Processes. There may be still activity on the system. |
|
|
|
||
Cause |
Araxi is a service that starts and monitors Prinergy processes, like daemons. There are some processes that Araxi does not directly launch, but does monitor, such as PJobD.exe. There is a limit to how many processes Araxi can monitor. The limit is about 59 processes. This limit can be reached if there are many jobs open at once. | |
|
|
||
Solution |
1) Shutdown Prinergy from Prinergy Administrator. 2) Check with NT Task Manager to ensure no Prinergy processes are running. 3) Restart Prinergy from Prinergy Administrator. 4) Limit the amount of open jobs to approximately 30. Permanent fix: Patch 38 modifies araxi.inf so that araxi.exe no longer monitors PJobD.exe in 1.1. Get this patch from the downloads page. Araxi.exe cannot monitor more than ~59 processes. The only process being monitored that can grow significantly in number is PJobD.exe because a copy of it is created for each active job. By removing PJobD.exe from the list of monitored processes Araxi.exe is much less likely to run into the limit of ~59 processes. Permanent fix: Prinergy 1.1 |
|
|
|
||
See also |
||
|
|
||
Keywords |
administrator, Windows NT |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||