Trying to access my ASP.NET page on my local machine's IIS and I get the following error:
------------------------------
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.
------------------------------
Event Viewer says:
Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1084
Date: 9/9/2004
Time: 10:04:32 AM
User: N/A
Computer: WSENQ--00370PDR
Description:
aspnet_wp.exe could not be started. The error code for the failure is 80004005. 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.
------------------------------
Running XP-Pro-sp1, .NET 1.1, IIS 6.0sp1I had the same problem on my machine this morning, it is 6:01 the next morning and I finnaly fixed it.
At first I had a machineName/acountName login fail error, then I changed a lot of seeting and got the error that you got: server application unavailable.
I uninstalled visual studio 2002, sqlServer because I changed so many things in there I could not fix them at my skill level. Then reinstalled them.
Then I found the following web page: http://aspnet101.com/aspnet101/tutorials.aspx?id=23
Followed the directions to a tee, but make sure in:
Step 1: Creating a Trusted SQL Server Connection
that you ALSO: not only perform the step for the administrator account but, also for the
* ASPNET_WP ACCOUNT*
Follow the rest exactly like it says. the rest of the steps only need to be performed once.
and it will work.
Hope this helps
Tom
What you need to do is go to the machine.Config file, which is located at:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\CONFIG
Go to the line:
<processModel enable="true" timeout="Infinite" idleTimeout="Infinite" shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000" restartQueueLimit="10"memoryLimit="60" webGarden="false" cpuMask="0xffffffff" userName="machine" password="AutoGenerate" logLevel="Errors" clientConnectedCheck="0:00:05" comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate" responseDeadlockInterval="00:03:00" maxWorkerThreads="20" maxIoThreads="20"/
Check the bold item in the above statement, and replace it with a higher number. That number is a percentage of the total main memory that is being used by the asp.net engine. The higher the better for your application, the worst for your machine performance.
Regards.
Hi Haidar,
What are you saying? How come the memory limit affect what the users are seeing. As you can see, they are talking about the permission issues, how could a memory setting fix it. I am sorry I am not trying to ridicule it. But, What are you talking about
Thanks
Hello, this error message usually happens if you are running any application that requires much of the memory. I had this once and I was able to solve it this way. It might be this solution, but what should be done right now, is to apply this solution and see what happens.
Regards.
Hmm. It is because the aspnet_wp could not be started when you debug with the VS.NET. There is a fix for this from Microsoft. Please take a look at the article.
http://support.microsoft.com/kb/820747/EN-US/
May be it was a coincidence that it seem to work after you change the memoryLimit setting. But I sincerely dont believe it has anything to do with aspnet_wp running
Anyway Take it easy
0 comments:
Post a Comment