remote debug asp.net

[hui]

Hi,

I am having trouble making my new machine to debug asp.net remotely.
The IIS runs at a win2000 server (sp 4), and my old win2000 client
machine works well with it. However, my new machine has xp pro
installed and it has trouble to start a debug process. The error
message says:
"Error while trying to run project: unable to start debugging on the
web server. The debugger component on the server failed to connect to
the local machine. Click help for more information"

If I try to manually attach to the aspnet_wp process on the server, I
get an error saying "Unable to attach to the process. Access is
denied".

The xp machine can debug asp.net locally.

All three machines are in the same domain.

I don't believe it is an account privilege issue as my account has
local admin role on all three machines.

Any suggestions are welcome.

 

[Teemu Keiski]

Hi,

see information provided in this KB article:

Overview of the "Impersonate a Client After Authentication" and the "Create
Global Objects" Security Settings (821546.KB.EN-US.2.2)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;821546

 

[hui]

Thanks for your reply, but it failed to solve my problem.

When I try to attach to the aspnet_wk process with only the "common
language runtime" selected, I got the following error similar to that
shown on auto debug:
"Unable to attach to the process. The debugger component on the server
failed to connect to the local machine."

The help message titles with "Remote Debugging Across Domains",
suggesting DCOM security is the issue.

However, I've confirmed with system admin that the machines are in the
same domain. I can't follow the workaround of changing local security
policies because the server is not xp.

I have managed to do remote debug to a win2k pro machine running full
vs.net. So I suspect somehow xp pro & win2k server don't like each
other.

 

[hui]

After more intensive googling, I think I have found a solution.
http://support.microsoft.com/default.aspx?scid=kb;en-us;833977&Product=vsnet

After I change the dcom configuration (and reboot) it all looks fine.

However, I still can't figure out why I could debug on a win2k pro
machine without such change. Perhaps the full vs.net makes the
difference, or because I access it through frontpage extension instead
of file sharing. I believe a proper answer will benefit future
googlers.

Thanks,

Hui