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 www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: ASP.NET 1.1.4322.0|
aspnet_wp.exe (PID: 2576) stopped unexpectedly.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a PID?
What is the .NET framework?
This event might occur when you use the Response.BinaryWrite method to download files that are 400 MB or larger from an ASP.NET page. See ME821387 to find out the cause of this problem and for a hotfix applicable to Microsoft Visual Studio .NET (2002) and ME823409 for a hotfix applicable to Microsoft Visual Studio .NET 2003.
This error occurs if the .NET runtime cannot dispose of all of the threads when the runtime tries to unload the application. See ME321564 for a hotfix applicable to Microsoft ASP.NET.
See ME912356 for a hotfix applicable to Microsoft Content Management Server 2002.
See ME942086 for a hotfix applicable to Microsoft .NET Framework 2.0.
See ME823015 for a hotfix applicable to Microsoft .NET Framework 1.1.
See ME326366 and ME812406 for additional information about this event.
Brian K. Miller
A page I found suggested changing the responseDeadlockInterval attribute in the machine.config file from responseDeadlockInterval="00:03:00" to responseDeadlockInterval="00:10:00" which seemed to do the trick. Make sure you restart IIS after making this change.
This event also occurs if you have written an application that runs in an infinite loop. When you kill the application, you will receive this event.
Change the application setting for the website, which you will find under IIS Console. There is a button Configuration. There you will find a checkbox "Cache ISAPI Application". For asp.net this option must be enabled, otherwise you get this error.
From a newsgroup post: "My problem was an oledb driver for Sybase 7. In my case the only driver I could get to work with .Net was 126.96.36.199 patch".
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated