@ben-hochstedler
Forum Replies Created
-
AuthorReplies
-
Thanks for the reply. I’ll have to look into that as the possible root cause. I’ve identified two workarounds for the problem:
Don’t read the output from hciprocstatus – just look at the exit code and use -p and -e options (the bgerror in tcl happens because of a pipe failure–if there’s no redirection of its stdout/stderr, the bgerror does not occur)
- Add file to the site to force hciprocstatus to exit with the following tcl proc:
Quote:proc bgerror err {
exit 69
}
I get the same error occassionally when running hciprocstatus (run once a minute to watchdog processes):
Quote:bgerror failed to handle background error.
Original error: broken pipe
Error in bgerror: invalid command name “bgerror”
Although I don’t get the other error messages that hciconnstatus produced. I too have found that rebooting is required to clear the condition.Have you seen the problem happen again?
What OS did it happen on?
Any further clues what caused it?
I’m running:
Windows 2000 Server SP4
QDX 5.2
Only 512KB is allocated for non-interactive processes’ heap on Windows (NT, 2000, XP, 2003, etc). Too many processes in QDX will eat it up, and occassionally you’ll see the following if another non-GUI process is started & not enough heap space is available: Quote:Application popup: cmd.exe – Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.
The command can be any command that is run under a non-interactive service (a service that is not marked as being able to interactive with the Windows desktop).
Workarounds:
Mark QDX service as being able to interactive with desktop (will use the desktop heap space for which there’s by default 4MB)
- Consolidate threads into fewer processes
- Increase the non-interactive heap space:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824422 ” class=”bbcode_url”> http://support.microsoft.com/default.aspx?scid=kb;en-us;824422 Quick instructions for option c:
In Registry Editor, locate the following registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerSubSystems
- Open the “Windows” value, locate the SharedSection parameter string in the Value field, and change the 3rd & 4th parameters from “512,512” to “2048” (a 4th parameter is actual invalid and is ignored if present).
- Close the Registry Editor and reboot the system.
Ben Hochstedler
Lead Software Engineer
GE Healthcare, Milwaukee, WI
-
AuthorReplies
