Debugging application that is hosted on a Domain Controller

  • Thread starter Thread starter Drunken Coder
  • Start date Start date
D

Drunken Coder

I have a small network setup in my home where I have my workstation which is
WindowsXP Home Edition and a server running Windows 2000 Server configured
as a domain controller. The domain controller has Visual Studio.NET
installed on it and IIS is configured. This machine is also hosting my SQL
Server 2000. Everything except debugging seems to be working. I can connect
to the machine from my remote workstation and develop as well as develop
locally I just can't debug. I have followed the information in Microsoft
Knowledge Base Article - 315158 to allow debugging but still no luck. When
I try to debug locally I get "Error while trying to run project: Unable to
start debugging on the web server. Catastrophic failure." When I try and
debug from my remote workstation I get: "Error while trying to run project:
Unable to start debugging on the Web server. Access is denied.This seems to
be because the "Network Access: sharing and security model for local
accounts' security policy does not allow users to authenticate as
themselves.This can be configured with the Local Security Settings
administration tool." I check this tool on the server and found nothing I
could modify. I just reloaded this server also so I am confident that it is
configured properly. No applications other than SQL or Visual Studio.NET
have been installed on this marching. Can anyone point me in the right
direction so that I can enable debugging on my domain controller and
preferable be able to debug remotely.

Thanks in advance

Steve
 
I have made a little bit of progress on this finally. I widened my search of
the knowledge base to include all microsoft products and found a knowledge
base article regarding this problem. It appears it's cause by installing SP4
on Windows2000 prior to installing Visual Studio.NET
http://support.microsoft.com/default.aspx?scid=kb;en-us;827559 has all the
details. After completing the procedure from this article I am now able to
debug on the server itself but still get the same error when I try to debug
remotely. Has anyone seen anything on this remote debugging issue?

Steve
 
Back
Top