Event ID 1000 Source .NET Runtime 2.0 Error Reporting
| Event ID | 1000 |
| Source | .NET Runtime 2.0 Error Reporting |
| Type | Error |
| Description | Faulting application <application name> version <application version> stamp 42435be1 faulting module <module name> version 0.0.0.0 stamp 00000000 debug 0 fault address 0x001f0001. |
| English, please! | This information is only available to subscribers. An example of English, please! |
| Concepts to understand |
How can an application become faulty? What is the fault address that some error messages provide? What is the .NET framework? |
| Comments |
David Florea
Application: Addusr.exe - Iin Exchange 2003 SP2, if the repair of .NET 2.0 doesn't succeed, turning off DEP for that application fixes the problem. Mihai Andrei - Application: microsoft.office.project.server.queuing.exe - See M953478 for a hotfix applicable to Microsoft Office Project Server 2007. - Application: devenv.exe - See M956322. - Application: snlreceiver.exe - See M947981 for a hotfix applicable to Microsoft BizTalk Server 2006 - Application: owstimer.exe - See M949399 for a hotfix applicable to Microsoft Windows SharePoint Services 3.0. This problem occurs when the pixel dimensions of icons in the content share are asymmetrical. See M942687 for information on how to solve this problem. Ionut Marin See M913384 for a hotfix for Microsoft .NET Framework 2.0. See M908077 for information on how to troubleshoot Microsoft .NET Framework 2.0 installation issues. If this event appears when you try to migrate a mailbox from Microsoft Exchange Server 2003 to Microsoft Exchange Server 2007, M948666 suggests to Download and then install Update Rollup 2 for Exchange 2007 Service Pack 1. Anonymous This error also occurs when you're missing an assembly. I created a .Net application that used assemblies that were in the GAC on my development computer, but not on the target computer. Adding the assemblies to the target computer solved the error. Mark Ball Microsoft IIS 6.0 offers the ability to isolate a web application by means of an Application Pool. Every Application Pool runs its own Worker Process (w3wp.exe). The Default Application Pool worker process shuts down after being idle for some time (20 minutes by default). Also, the rapid-fail protection feature will disable the worker process if there are a number of failures within a stipulated time. According to Microsoft, "An IIS 6.0 application pool may unexpectedly exit when a worker process shuts down or is recycled". See MS article M918041. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! |
| Links | M908077, M913384, M918041, M942687, M947981, M948666, M949399, M953478, M956322 |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Custom search | The custom search information is available to subscribers only. |
| Feedback | Send comments - Notify me when updated |
| Print version |