Last post Oct 08, 2009 07:26 AM by raheelcsku
Jan 05, 2006 05:48 PM|asn1986|LINK
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.
Jan 05, 2006 09:53 PM|aspnewbieperson|LINK
Have you specified in Computer Management to run your application as 2.0?
If you want only specific applications to run 2.0 then you have to do this for each virtual directory.
If you want all your application to use 2.0, you can do the whole of localhost.
The way I do it is:
This will affect ALL asp applications, although local version selection for each virtual directory should take precedence.
I hope this helps.
Jan 06, 2006 10:01 AM|DSetzer|LINK
I'm exhibiting the same/similar behavior as the original poster and have confirmed what you've suggested - that my apps are setup to run ASP.NET 2.0.
Any other ideas?
Jan 06, 2006 05:27 PM|asn1986|LINK
Jan 04, 2007 11:32 AM|mto_programmer|LINK
May 14, 2008 09:43 AM|JimmySeal|LINK
That was just what the doctor ordered. I'd figured out the first part, but not the second part and I was going out of my mind.
Thank you so much. [:D]
Jul 22, 2008 06:39 AM|jkk102|LINK
That worked for me too! Thanks guys, was really stressed about it :D
Aug 28, 2008 05:04 AM|ryansh|LINK
I have done what you have said but get the following error message in the log file:
Starting service: StartService failed with HRESULT 8007042d: 'The service did not start due to a logon failure. ' 2008-08-28 10:40:58 Failure Starting service: aspnet_state: StartServiceByName failed with HRESULT 8007042d: 'The service did not start due
to a logon failure
I think someone may have deleted the user accounts needed, please can you assist.
Apr 23, 2009 10:20 AM|asaf meir|LINK
iisreset is required.
Oct 08, 2009 07:26 AM|raheelcsku|LINK
I have been facing the same error but when I follow the same procedure :i-e., Run aspnet_regiis /i and then iisrest and now I am happy with my production server