Re: vs2005 debugging on ws2k3 server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi Rahul ,

neither suggestion has had any effect.

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 I "Start Without Debugging" then things work as they should and i get IIS
log entries
If I "Start Debugging" then I get the error dialog and there are no IIS log
entries whatsoever.

Gerry


"Rahul Soni" <RahulSoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D86FCEFC-FB9C-46E5-93DD-4E843C00CC28@xxxxxxxxxxxxxxxx
> Hmm, yes you are right. It is indeed because of the Kerberos tickets.
>
> Another couple of things to check and if it doesn't work, u may proceed
with
> what you decided...
>
> 1) http://support.microsoft.com/?id=215383
>
> First follow the above article and if that doesn't help you can try the
> following as well...
>
> 2) In your Internet Explorer settings.... Go to the Advanced tab and
uncheck
> "Enable Integrated Windows Authentication (requires restart)"
>
> Restart your IDE and try debugging again.
>
> Also, if you could just share the IISLogs containing the debug verbs I
would
> have got ample clues to figure out what went wrong. Let me have those if
> possible...
>
> --
> Thanks,
> Rahul Soni
>
> [A problem well stated is a problem half solved!!]
>
>
>
>
> "gerry" wrote:
>
> > this is definitely a kerberos related problem - here are the event log
items
> > recorded when I try to debug :
> >
> > Security
> > Date: 12/23/2005
> > Source: Security
> > Time: 9:15:33 AM
> > Category: Logon/Logoff
> > Type: Failure Aud
> > EventID: 537
> > User: NT AUTHORITY\SYSTEM
> > Computer: MYPC
> >
> > Logon Failure:
> > Reason: An error occurred during logon
> > User Name: gerry
> > Domain: MYDOMAIN
> > Logon Type: 3
> > Logon Process: èuZ
> > Authentication Package: NTLM
> > Workstation Name: MYPC
> > Status code: 0xC000006D
> > Substatus code: 0x0
> > Caller User Name: -
> > Caller Domain: -
> > Caller Logon ID: -
> > Caller Process ID: -
> > Transited Services: -
> > Source Network Address: 10.0.0.30
> > Source Port: 0
> >
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >
> > System
> > Date: 12/23/2005
> > Source: Kerberos
> > Time: 9:15:33 AM
> > Category: None
> > Type: Error
> > EventID: 3
> > User: N/A
> > Computer: MYPC
> >
> > A Kerberos Error Message was received:
> > on logon session
> > Client Time:
> > Server Time: 14:15:33.0000 12/23/2005 Z
> > Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN
> > Extended Error:
> > Client Realm:
> > Client Name:
> > Server Realm: MYDOMAIN.CA
> > Server Name: krbtgt/MYDOMAIN.CA
> > Target Name: cifs/test.mypc.mydomain.ca@xxxxxxxxxxx
> > Error Text:
> > File: 9
> > Line: ae0
> > Error Data is in record data.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
> >
> >
> > I have looked into this and am just baffled by the whole kerberos thing.
> > I don't have time to waste screwing with this so I have decided to open
my
> > http web site as a file based site in vs that way i can debug in vs and
test
> > across the network as well.
> >
> > Gerry
> >
> >
> >
> >
> >
> >
> > "Rahul Soni" <RahulSoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:8F55DF32-9C25-4BD3-895C-AEC33C08F3C6@xxxxxxxxxxxxxxxx
> > > By default this site is in the internet zone although I would have
thought
> > it
> > > should be intranet as it is a local domain ie.
http://dev.mydomain.com I
> > set
> > > the setting is as stated for both internet & intranet adding the site
to
> > the
> > > intranet zone made no difference
> > >
> > > ---> The sites typically show in the Internet Zone because it has two
dots
> > > in the name. Can you try removing one of the dots for testing purposes
and
> > > see if that helps?
> >
> > I just manually added the site to the intranet zone - no effect.
> >
> > >
> > > What about the IISLogs? Can you paste the entries after you create a
new
> > app
> > > and try to debug it?
> > >
> > > nada - no entries in any log files anywhere that I can find. there are
the
> > > expected etries if I start without debugging but nothing if I try to
> > debug.
> > >
> > > ---> Well, that doesn't look good. There should be some entries with
debug
> > > verb sent and some error codes showing up. Search for the word "debug"
in
> > > your IISLogs and you should find them. If you don't see "debug" verbs
> > being
> > > sent at all check your IIS Settings. As a thumbrule, there has to be
DEBUG
> > > verb in your IISLogs when you try to debug any app.
> >
> > well you are assuming that a request is being sent to IIS.
> > it looks to me like the process is never even getting to the point of
> > actually sending any type of request to IIS.
> >
> > >
> > > HTH,
> > > --
> > > Thanks,
> > > Rahul Soni
> > >
> > > [A problem well stated is a problem half solved!!]
> > >
> > >
> > >
> >
> >
> >


.



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: 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)
  • VS.NET 2003 Debug Problem in IIS
    ... didn't use yet, also IIS LockDown Tool. ... After the uninstall process I ... VS.NET 2003 does not work anymore in debug mode. ... application also without the debug support results much more strange, ...
    (microsoft.public.vsnet.debugging)