Can't set application protection to high :(

Tech-Archive recommends: Fix windows errors by optimizing your registry

wuhy80_at_gmail.com
Date: 02/25/05


Date: 24 Feb 2005 22:45:19 -0800

Hi!

I'm trying to set an application in IIS to run as an isolated process,
as that seems to be required to debug it. Somehow I get the message
"User/Password authentication failed" when I try to set application
protection to high.
Anyone know why? I'm logged on as admin. and I HAVE got
axx to the wwwroot folder :(



Relevant Pages

  • Re: VS2008 HTTP 403 Help!!
    ... Highlighting the default.aspx before debug start or explicitly setting Default.aspx to the start page works. ... That's an alleged workaround which doesn't work, not a solution to the bug. ... Seems like the web app project does not default to the ONLY aspx in a project during debug run. ... That error is caused by a virtual directory not being configured as an application in IIS. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: IIS ASP.NET 2.0 Bug
    ... It was when your tone turned condescending and insulting, ... debug, is to identify problems". ... identified that the problem is with IIS and not my code. ... I did appreciate your help in telling me how to turn Casini off. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Debugging returning 401 HTTP error
    ... I enabled it again and now I can debug! ... > What about the operation system and the FRAMEWORK and IIS version? ... > ASP.NET Debugging to work. ... > NTLM authentication was failing because HTTP Keep-Alives were disabled. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: vs2005 debugging on ws2k3 server
    ... I can't share the IIS logs with you, as I stated earlier, there are no ... entries in the iis logs when this error occurs. ... if you could just share the IISLogs containing the debug verbs I ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VS2008 HTTP 403 Help!!
    ... the web app project does not default to the ONLY aspx in a project ... Highlighting the default.aspx before debug start or explicitly setting ... That error is caused by a virtual directory not being configured as an ... Check in your IIS Manager, and make sure you created a virtual ...
    (microsoft.public.dotnet.framework.aspnet)