IIS Hang - ISAPI w3svc Deadlock

Hi All,

I've got a a bit of an issue with IIS locking up.

We've managed to tie the crash to when the Content Managment System (which
is on another server) publishes it's content to the public facing web server.
Sometimes when this publish occurs IIS will simply hang on the public facing
server and the only way to get it functioning again is to run an 'iisreset'.

When the hang occurs I get the followin error in the event log:

Event Type: Warning
Event Source: W3SVC-WP
Event Category: None
Event ID: 2262
Date: 15/10/2007
Time: 09:53:31
User: N/A
Computer: SVR-WEB02
Description:
ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll'
reported itself as unhealthy for the following reason: 'Deadlock detected'.


Has anyone got any ideas on a solution?

RE: IIS Hang - ISAPI w3svc Deadlock

Hi Steven,
We are facing the same issue. Did you manage to find a way around this issue
yet?.

BTW, what CMS are you using?. We are using Tridion CMS to publish files to
our servers. I have read in one of the posts that the COM interop could be
causing the issue (Tridion CMS uses COM interop on the presentation side and
as such we are looking at the solution suggested at
http://support.microsoft.com/default.aspx?scid=kb;en-us;9212 17&sd=rss&spid=8291)

Regards,
Sajit

"Steven Askwith" wrote:

> Hi All,
>
> I've got a a bit of an issue with IIS locking up.
>
> We've managed to tie the crash to when the Content Managment System (which
> is on another server) publishes it's content to the public facing web server.
> Sometimes when this publish occurs IIS will simply hang on the public facing
> server and the only way to get it functioning again is to run an 'iisreset'.
>
> When the hang occurs I get the followin error in the event log:
>
> Event Type: Warning
> Event Source: W3SVC-WP
> Event Category: None
> Event ID: 2262
> Date: 15/10/2007
> Time: 09:53:31
> User: N/A
> Computer: SVR-WEB02
> Description:
> ISAPI 'c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi. dll'
> reported itself as unhealthy for the following reason: 'Deadlock detected'.
>
>
> Has anyone got any ideas on a solution?