IIS 5 & IIS 6
IIS 6 requiring frequent iisreset
Last post Jan 26, 2009 07:39 PM by Rovastar
Jan 26, 2009 11:16 AM|kefka|LINK
For a while now, I've had a Windows 2003 Enterprise box running IIS 6 in native mode which experiences hangs on a daily basis. While it is in this "hung" state, the website is not accessible to any users and the only thing that seems to get it working again
is by issuing an iisreset /restart command from the server. It seems to happen very sporadically. Some days it might be fine, others it might hang 2 or 3 times a day. Well, it happened this morning a little after 6AM and I got a phone call asking me to
look into it. At this time, I noticed that the w3wp process was still showing up as a running process in the task manager, so I used DebugDiag to take a dump of that process before restarting the IIS services. However, I am not a developer/debugger, so I
was hoping someone here might be able to put what I'm seeing with DebugDiag into layman's terms. I have just provided the Analysis Summary below. I can also provide any other information needed. Thanks in advance for any assistance you can provide.
Jan 26, 2009 11:41 AM|abs_jaipur|LINK
The best way to find this cause is just check if there is any event ID for it in event viewer and which will perfectly show the exact cause.
Are you running multiple websited are just single.
Jan 26, 2009 11:51 AM|kefka|LINK
The only things that jump out at me from the event logs are these messages, which seem to be appearing rather often throughout each day.
Warning: IIS log failed to write entry, File /LM/W3SVC/1/Root/Imaging/global.asa Line 104 The Web logon identity for this user and library was lost.. .
A process serving application pool 'ImagingAppPool' failed to respond to a ping. The process id was '3672'.
It's a single website, but we do have a separate application pool in addition to the default app pool that contains a custom asp application that interfaces with FileNet.
Jan 26, 2009 02:29 PM|clinkmeister|LINK
The dump has the application pool name inside the file name of the dump file: ImagingAppPool.
I would say that the developer of the application that is running is the only one who can probably solve this problem. The dump description is actually pretty details, indicating a deadlock. One thread owns the lock, and another thread is attempting to
It sounds like a problem in the custom app.
Jan 26, 2009 07:39 PM|Rovastar|LINK
I agree. It is likely an app problem you know you app pool and the site.
I am surprised you get nothing in the event log.
The IIS Log file should also give you a good indication of what files are being accessed/processed at the time. Look out for long running pages and of course any http status errors or win32 errors. I presume this is an asp page?
Note down when the lockup occurs and see if any pages/etc are the same every time. It is all about gathering more information to paint a picture,