Determining why a Win2K task died, traceback etc.

[Pat Coghlan]

I have an application consisting of software clients on various workstations that receive updates that are displayed in a window. The updates are forwarded by a task running on a Win2K server.

Several instances of this system are in use across the country, but in one location the server task suddenly dies, leaving blank screens on all the client machines. This doesn't happen in any of the other locations.

It would appear that the server task runs into difficulty and crashes, and the parent service does not restart it (this is a 3rd-party application, but I know about the task that dies).

Question: When a Win2K task dies, is there a .dmp or other file created that I can perform a post-mortem on???

[ɹəuəllıʍ ʇɐb]

Welcome to the Windows Forum.

I believe the first place to look is in the Event Viewer; you may get the most essential information on why the task died. I don't know about a possible dump - this may be a build option of the original application itself.

Can you get any support / information from the people who created that software?

[Pat Coghlan]

Welcome to the Windows Forum.

I believe the first place to look is in the Event Viewer; you may get the most essential information on why the task died. I don't know about a possible dump - this may be a build option of the original application itself.

Can you get any support / information from the people who created that software?

Working on that, but apparently Win2K has a utility called Dr Watson which catches these exceptions and provides some traceback information.

[ɹəuəllıʍ ʇɐb]

Ah, yes, Dr. Watson... See if this helps

http://support.microsoft.com/kb/308538