Windows server in hung state

If a server became unresponsive (Hung state) which caused the applications on that server to fail. How would we check in the event logs to clarify if a server has become in a hung and un-responsive state? We had this issue where a server had a blip and caused the applications to fail on it. We know the server didnít not go off live as we have done network checks and you could ping the server.

For example explorer.exe if you close that process will cause underlying applications to fail. Is explorer.exe the same on windows server 2003? What would we need to look for in the logs to see if the server did hang? .

This was in other forum - Internet/Connectivity - Application Servers. Cannot delete from their?

If the server is truly hung there may not be any event logged. If you are able to ping the server then it is not competely hung. If you have local access to the server, have you tried Task Manager? Did you look at any of the event logs?

If the server is truly hung there may not be any event logged. If you are able to ping the server then it is not competely hung. If you have local access to the server, have you tried Task Manager? Did you look at any of the event logs?

Joe

Hi Joe,

Nothing from the event logs or VM logs. All we can see is that the server lost connection to DB2 on a Linux box. Do you know much about DB2 ?

Have you checked that other network access is OK?
Does this happen often?
What is running virtualized?
Is the Windows OS up-to-date with patches?
Most data base software will close open connections after a period of inactivity. Have you checked the DB2 configuration?
Has DB2 or the application program been updated recently?

If it's a Virtual machine, make sure you don't have any Snapshots created by something crazy like a backup program. This will cause unpredictable behaviors like this. Please go to your Snapshot Manager of the VM and verify that there is not snapshot of that particular machine.