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 could not be started. The error code for the failure is <error code>. This error can be caused when the worker process account has insufficient rights to read the .NET Framework files. Please ensure that the .NET Framework is correctly installed and that the ACLs on the installation directory allow access to the configured account.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the .NET framework?
What are the worker processes?
In my case, I had to reset the password for the ASPNET account and restart IIS and the ASP.NET State Service.
In my case, I found that the aspnet_wp process was duplicated. I only terminated one process and the issue was resolved.
In my case, I found that the local security policy denied the ASPnet account logon locally rights. I changed this, rebooted the server and it worked.
Check to see if the ASPNET account is locked out.
- Error code: 80004005 (Error code 80004005) - This problem may occur when you install any .NET Framework service pack on a member server. See ME887286 for a resolution. Also, see ME820747 and the link to "Smartax Support Article ID: 000092" for additional information about this event.
I have this problem in combination with WSUS on a Windows 2000 server. By putting information from different newsgroups together, I was able to create a batch file to resolve this problem, as it continuously re-occurs:
net stop iisadmin
net start iisadmin
net start w3svc”.
We installed ASP .Net 1.1 and ran into this issue. This error appears if the application is installed under local admin and a domain user account running IIS tries to utilize the framework. Reinstalling ASP .Net 1.1 under a domain account with local admin rights will correct this problem. We also found that installing SP1 for .Net Framework 1.1 would also cause this error because it resets the ASP .Net machine account access rights on the server.
From a newsgroup post: "If you run the patch from MS03-32-issue on a machine with ASP.NET V1.0, it works fine, it corrects the defect. According to Microsoft this problem should not appear in ASP .NET V1.1, but in my case this is exactly what happened. The batch file however, will not run on a machine with ASP.NET V1.1. To workaround this limitation here is how I modified the batch file to run on ASP .NET V1.1:
In the downloaded batch file make the following changes:
1. REM if exist “%SystemRoot%\microsoft.net\framework\v1.1.4322\mscorlib.dll goto v11_installed”
2. REM "Changing to the Framework install directory" cd /d %SystemRoot%\microsoft.net\framework\v1.1.4322.
After this the batch file should run. In my case this fix worked, I can now access and create ASP.NET projects without problems".
- Error code: 80070005 - As per Microsoft: "To work around this problem, verify that the ASPNET account has the correct user rights". ME811320 provides information on how to do that.
- Error code: 80070545 - Happened after an upgrade of .NET Framework from 1.0 to 1.1. See the links below for an article on how to create a domain account for ASP.NET.
Error code 80004005 - This may occur if the web server where ASP.NET is installed is an Active Directory domain controller as well. See ME315158.
|Private comment: Subscribers only. See example of private comment|
|Links: ME315158, ME811320, ME820747, ME887286, Error code 80004005, Smartax Support Article ID: 000092, How to create a domain account for ASP.NET, MS03-32-issue|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated