Visual Studio .NET 2003 and Visual Studio .NET 2002

Re: Can't attach debugger

Thomas Sun – MSFT — Tue, 02 Jun 2009 09:47:31 GMT

Hi,

To debug .NET applications, developers not only need the capabilities provided as members of the “Debugger Users” but also need to log into the same account that runs the ASPNET worker process when debugging an ASP.NET web service.

For more information, see http://download.microsoft.com/download/f/f/8/ff8c8040-d1a7-4402-90df-5d1aaa7d37af/dotNETDevVSGroups.pdf (Section: Debugging ASP.NET Web Applications and Services ).

I look forward to receiving your test results.

Re: Can't attach debugger

amisol — Thu, 28 May 2009 05:15:58 GMT

So, is there a way to run the asp.net worker process under my user? or am I stuck stuck...

Re: Can't attach debugger

nikki_doer_of_things — Thu, 28 May 2009 02:52:54 GMT

I think you're stuck? I've never tried without being in the admin group, but here's what I found in the docs.

Visual Studio remote debugging components must be installed on the server you want to debug. For more information, see Setting Up Remote Debugging.

By default, the ASP.NET worker process runs as an ASPNET user process. As a result, you must have Administrator privileges on the computer where ASP.NET runs to debug it. The name of the ASP.NET worker process varies by debug scenario and version of IIS. For more information, see How to: Find the Name of the ASP.NET Process.

http://msdn.microsoft.com/en-us/library/z3bxds0s.aspx "To debug a process that is running under another account name: Your Windows login account has to be a member of the system administrators group on the remote computer."

Can't attach debugger

amisol — Thu, 28 May 2009 00:40:46 GMT

I'm logging to a citrix box which I'm part of the VS Debugger Users. I tried debugging the application but when I try to attach the w3wp.exe I get access denied.

What is the policy our admin need to set up in order to give us the ability to attach the debugger? We looked at the Debug Program under user rights assignment with no success.

Developers can't be part of the administrator group (that's the only way we could make this work).