W3svc-Wp error

Hi,
Event id : 2262 w3svc-WP

ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy for
the following reason: 'ASP unhealthy because 100% of executing requests are
hung and 8% of the request queue is full.'.


Event id : 1013 w3svc

A process serving application pool 'DefaultAppPool' exceeded time limits
during shut down. The process id was '4832'.

Event id : 1041 w3svc

The 'Virtual Site' '1035277248' failed range validation for property
'ConnectionTimeout'. The configured value '99999' is outside of the range
'0' to '65535'. The value will default to '120'.

Above i had discussed about the problem which is currently running
on our Windows2003 server is disclosed. For this error when i surfed for
solution Article Id :- 821268 is provided as solution. Which didn't worked.
So please help me out to fix the issue.

Re: W3svc-Wp error

On Nov 21, 11:10 pm, Bala wrote:
> Hi,
> Event id : 2262 w3svc-WP
>
> ISAPI 'C:\WINDOWS\system32\inetsrv\asp.dll' reported itself as unhealthy for
> the following reason: 'ASP unhealthy because 100% of executing requests are
> hung and 8% of the request queue is full.'.
>
> Event id : 1013 w3svc
>
> A process serving application pool 'DefaultAppPool' exceeded time limits
> during shut down. The process id was '4832'.
>
> Event id : 1041 w3svc
>
> The 'Virtual Site' '1035277248' failed range validation for property
> 'ConnectionTimeout'. The configured value '99999' is outside of the range
> '0' to '65535'. The value will default to '120'.
>
> Above i had discussed about the problem which is currently running
> on our Windows2003 server is disclosed. For this error when i surfed for
> solution Article Id :- 821268 is provided as solution. Which didn't worked.
> So please help me out to fix the issue.



This looks like a serious bug in your ASP application. You must fix
the application to address your issue.

These events say your ASP application has bad code that is taking too
long to process a request. It is taking so long that it causes ASP to
queue requests waiting for your application to finish, and it also
takes forever to finish when IIS is trying to recycle the application
pool. Furthermore, it appears that you have tweaked the
ConnectionTimeout to an out-of-bounds value, probably because of this
bad ASP application.

Bottom line -- fix the ASP application to not run so slowly, and you
will find all these events magically go away and you don't need to
change connectionTimeout to 999999 at all.

Until you fix the ASP application, you will keep getting these
problems with no way to address them that is not merely a temporary
bandaid.

FYI: You have an ASP application. KB 821268 is for ASP.Net. The two
technologies are unrelated, so no surprise that it didn't work.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//