Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1003 Source: ASP.NET 1.0.3705.0

aspnet_wp.exe  (PID: <ID>) was recycled because it was suspected to be in a deadlocked state. It did not send any responses for pending requests in the last 180 seconds.
This problem can occur because of a memory leak in the BSTR object. See ME912356 for a hotfix applicable to Microsoft Content Management Server 2002.

When you perform a background batch compile, the compile may cause the Aspnet_wp.exe process to deadlock if all the worker threads are used. See ME821155 for a hotfix applicable to Microsoft ASP.NET 1.1.

This behavior may occur if an exception that causes process recycling is not processed completely. See ME840861 for a hotfix applicable to Microsoft .NET Framework 1.1.

This problem can occur when the ASP.NET worker process has been idle for the duration that is specified in the responseDeadlockInterval configuration setting in the Machine.config file. See ME841557 for details on how to fix this problem.
ME329956 provides a hotfix for this problem.

As per Microsoft: "This problem might occur because ASP.NET limits the number of worker threads and completion port threads that a call can use to execute requests. To resolve these problems, you can tune parameters in your Machine.config file to best fit your situation". See ME821268 for additional information.

As per Microsoft: "This behavior occurs if the ASP.NET worker process has been idle for the time that is specified for the responseDeadlockInterval configuration setting in the Machine.config file. This causes the deadlock detection mechanism in ASP.NET to recycle Aspnet_wp.exe. A slow write to the client may take longer than the value of responseDeadlockInterval". See ME328267 for a hotfix.

ME325947 also provides a hotfix, however this hotfix does not resolve deadlocks; this hotfix only provides instrumentation to troubleshoot and to diagnose deadlocks.

You might want to look at Crystal Care Technical Support ID: c2011424. It provides information on how to avoid this type of problems.
As explained in the description, there isn't anything required to do in order to fix the problem. See ME321792.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.