Groups | Blog | Home
all groups > visual studio .net debugging > september 2004 >

visual studio .net debugging : Debugger component on server failed to connect


dh
9/16/2004 8:07:22 AM
Trying to debug a simple "Hello World" ASP .Net web page or a simple Web
service.

Server: Windows Server 2003 Enterprise, Primary Domain Controller, Debug
components installed
Client machine: Windows XP Pro (SP2), User is member of Debuggers and
Administrators

Get the message:

"Error while trying to run the project. Unable to start debugging on the web
server. The debugger component on the server failed to connect to the local
machine."

I tried modifying the Machine.config file on the server, changing the
"username" attribute on the <processModel> tag from "machine" to "system"
(and restarting IIS), but this did not help.

I am able to run without debugging.

After attempting to run, I do see two w3wp.exe system processes on the
server (one Win32 type, the other .Net type). If I attempt to attach to
either of these, I get the message "Unable to attach to process. The
debugger component on the server failed to connect to the local machine."

Help!

Thanks
Dan H



dh
9/16/2004 5:48:53 PM
Also, I do not have the MS firewall enabled on either the development
Windows XP Pro machine, nor on the Windows Server 2003 remote machine...

Dan


[quoted text, click to view]

dh
9/16/2004 6:12:14 PM
Got it.

The key was enabling ANONYMOUS LOGON in the COM security options in dcomcnfg
as per the following KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;833977&Product=vsnet



[quoted text, click to view]

v-garych NO[at]SPAM online.microsoft.com (
9/17/2004 8:26:59 AM
Well, Daniel,

We are delight you resolved the problem quuuickly and also thanks for
sharing your experience in the newsgroup.


Good Luck!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Jason
9/30/2004 5:25:02 PM
This is not resolved. I'm having the same issues. So are others in the
community. Please help us out.

Latest error:

The debugger component on the server failed to connect to the local machine.

XP SP2 is installed on the client machine, Firewall is disabled
Windows2003 Server, tried this ANONYMOUS LOGON hint but with no luck
Also, in component services, controls read "Default COM Security Options"
and "Edit Defaults", not as posted.

Why hasn't this been patched or something yet?

Why doesn't it have a kb article (which is complete)?

Jason

[quoted text, click to view]
acgetchell
10/6/2004 3:29:08 PM
Agreed. This problem is not fixed. I've gone through:

http://www.dotnet247.com/247reference/a.aspx?u=http://msdn.microsoft.com/security/productinfo/xpsp2/default.aspx?pull=/library/en-us/dnwxp/html/xpsp2remotedebug.asp

http://www.dotnet247.com/247reference/a.aspx?u=http://support.microsoft.com/default.aspx?scid=kb;en-us;833977&Product=vsnet

http://support.microsoft.com/default.aspx?scid=kb;en-us;833977&Product=vsnet

In particular:

Install remote debugging:

msiexec /qb+ /i z:\vs_setup.msi NOVSUI=1 TRANSFORMS="z:\Setup\Rmt9x.mst"
SERVER_SETUP=1 ADDLOCAL=Full_Remote_Debugging

Add DOMAIN\Developers to local Debugger Users group
Add DOMAIN\Developers to local VS Developers group

Now add server to local Intranet site in IE

Add Autostart for ASP.NET State Service

Still blocking debugging, reboot

Add DOMAIN\Developers to Admin group, or follow directions here:

http://support.microsoft.com/?id=317290

Install Visual Studio Remote Components + VS gunk required

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vctskinstallingremotedebugmonitor.asp

Now add ANONYMOUS LOGON via:

http://support.microsoft.com/default.aspx?scid=kb;en-us;833977&Product=vsnet
AddThis Social Bookmark Button