I know that all you want to hear about is yet another non-
admin remote debugger problem but I'm really stumped.
Before you quickly reply, please note that I have spent
several days scouring the newsgroups, reading the How To
Solve Debugger Problems document, and KB articles like
306172.
Environment:
-Server: Windows Server 2003 Standard (newly installed
twice) with remote debugging components installed
-Client: VS.NET 2003 on both Windows 2003 (existing
install) and Windows XP (new install)
-Both Server and Client are members of same domain, same
subnet, same switch
-Project: very simple C# web application (as a test)
Rights/Settings:
-Debugger Users group
-VS Developers group
-IIS_WPG group
-SeDebugPrivilege (Debug programs)
-IIS vroot running in Application Pool running as me
-ACLs as defined in Developing Software in Visual
Studio .NET with Non-Administrative Privileges (url below)
-Server is listed in client's intranet/trusted sites
Error (after F5):
"Error while trying to run project: Unable to start
debugging on the web server. You do not have permissions
to debug the server. Verify that you are a member of
the 'Debugger Users' group on the server."
I have read, re-read, applied, and re-applied the steps in
Developing Software in Visual Studio .NET with Non-
Administrative Privileges
(
http://msdn.microsoft.com/library/en- us/dv_vstechart/html/tchDevelopingSoftwareInVisualStudioNET
WithNon-AdministrativePrivileges.asp). These have been
the most promising because with them, I am able to
manually attach but not auto-attach. I've tried changing
the <processModel> tag with the same results. If I add
myself to the Administrators group, it auto-attaches just
fine.
The only clue I'm left with is a security error in the
Event Viewer. I turned failure auditing on for everything
(including on the file system) and I get two copies of
this error each time I try F5. The source port changes
each time I try debugging.
-Category: Logon/Logoff -Type: Failure Audit -Event ID: 529
-User: NT AUTHORITY\SYSTEM -Computer: {Server name}
Logon Failure:
Reason: Unknown user name or bad password
User Name:
Domain:
Logon Type: 3
Logon Process: Kerberos
Authentication Package: Kerberos
Workstation Name: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: {Client IP}
Source Port: 1409
Any ideas on what I've missed? I don't know much about
Kerberos but everything else seems to be working fine.
Any help is greatly appreciated.
--Jared
