".NET Application failed to initialize" popup
-
I got a strange error yesterday evening on our batch server. A .NET 3.5 console application that never failed before displayed a pop-up saying: "Application failed to initialize properly (0xc0000142)" when the scheduler tried to launch it. The %ERRORLEVEL% was set to 128. When launching it again this morning, everything went well.
Obviously having a pop-up on a server is quite useless. I did find its contents back in the "System" eventviewer, logged as an information event. I suppose Windows 2003 knows it's a headless server and wants to preserve the content of pop-ups.
But when investigating, our support people didn't have the reflex to go through the informational events in the system eventviewer.
So my question is: is it possible to log these kind of pop-ups as errors in the event log, preferably in the Application event log? Is it possible to configure this?
-
@bjolling said:
Obviously having a pop-up on a server is quite useless.
Not the first time this sort of thing has been noticed. Unsure if the solution there is any use to you however.
-
@PJH said:
@bjolling said:
Interesting idea, but I'm not sure if that would be a solution. From the article I understood that you can hook into the message pump of your own application. But in this case I would need access to the messages of the application launcher of Windows.Obviously having a pop-up on a server is quite useless.
Not the first time this sort of thing has been noticed. Unsure if the solution there is any use to you however.Or I need a hook that gets called everytime a dialog box is created from no matter what application. Gonna look into this.
-
What causes the error? I have a lot of .net console apps that run from the scheduler, so if you find the fix I'd appreciate it.