Re: Debugging returning 401 HTTP error

From: James Bailey (junk_at_junk.com)
Date: 04/06/04


Date: Tue, 6 Apr 2004 09:00:16 -0700

Going down the list:

1. Yes, normal console apps can be debugged.

2. The service is enabled and running. Doing a -u and a -i didn't work.

3. I had turned this off while trying to fix all of this thinking that it
might be a problem. I enabled it again and now I can debug!

Thanks!

----
James Bailey
"Steven Cheng[MSFT]" <v-schang@online.microsoft.com> wrote in message
news:rmsEW22GEHA.3444@cpmsftngxa06.phx.gbl...
> Hi James,
>
> Thanks for your confirm. I'm glad that you've resolved the problem. And
the
> reason why my former messages lost may due to the the too big size make
> them get lost. Here is my initial reply
>
> ===============================================================
> Hi James,
>
> From your description, you failed to use F5 debug on an ASP.NET web app in
> VS.NET and you got the 401 error from the IIS log ,yes?
>
> What about the operation system and the FRAMEWORK and IIS version?
> Also, you've mentioned that you've tried many common steps on this problem
> still with no success. I also feel   a bit strange since all the steps
> you've tried not work at all. Here are some of my suggestions:
> 1. Is the normal console .net application able to debug correctly? If not
> you'd have to manually register the mscordbi.dll via regsvr32
>
> 2. Please check whether the "Machine Debug Manager" service is started
> properly. If no, please stop it and restart again. Also, as you mentioned
> that you've tried the aspnet_regiis -i to reinstall the ASP.NET, I think
> you can retry  this via the following sequence:
> aspnet_regiis -u
> aspnet_regiis -i
>
> 3.As you also mentioned that it seems that the http debug request is
denied
> from the IIS, I suspect that whether the problem is due to the Integrated
> autentiation in IIS. In other word, maybe  Windows Integrated (NTLM)
> authentication was failing in IIS, and this authentication is required for
> ASP.NET Debugging to work.
> NTLM authentication was failing because HTTP Keep-Alives were disabled.
You
> may have a view at the following kb article:
> #Web Browsers Receive "HTTP 401.5" Error When You Use Windows NT
> Challenge/Response
> http://support.microsoft.com/?id=288323
>
> #NTLM Authentication Is Lost on Every Call
> http://support.microsoft.com/?id=323683
>
> The above items are some additional ideas I've got from some former
similar
> cases(some others  finally ended with reinstall). If they still not work,
I
> think there maybe some strange problem occured in the IIS or asp.net
> internal. Then,  it would require intensive troubleshooting which would be
> done quickly and effectively with direct assistance from a Microsoft
> Support Professional through Microsoft Product Support Services if you do
> think it is an urgent issue.  Thanks.
> ======================================================================
>
> Also, I've tried sending it to you via email but the mail address seems
> unreachable. Anyway, Thanks again for posting here.
>
> Regards,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>


Relevant Pages

  • Re: Need help on debugging the code in .NET Web application.
    ... > I'm getting the following error while trying to debug the application. ... There are a couple of reasons why debugging fails: ... The IIS mappings are incorrect (very common when IIS installed after ... where Windows directory is normally either Windows or WINNT. ...
    (microsoft.public.dotnet.academic)
  • RE: error while trying to run project: Unable to start debugging on th
    ... Server side-error occured on sending debug HTTP request. ... > errors in web.config by doing a Debug.Start Without Debugging. ... > I checked my application virtual directory properties in IIS and found ...
    (microsoft.public.vsnet.debugging)
  • error while trying to run project: Unable to start debugging on the web server. Server side-erro
    ... Error while trying to run project: Unable to start debugging on the web ... Server side-error occured on sending debug HTTP request. ... I checked my application virtual directory properties in IIS and found ...
    (microsoft.public.vsnet.debugging)
  • error while trying to run project: Unable to start debugging on the web server. Server side-erro
    ... Error while trying to run project: Unable to start debugging on the web ... Server side-error occured on sending debug HTTP request. ... I checked my application virtual directory properties in IIS and found ...
    (microsoft.public.vsnet.debugging)
  • 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)

Loading