Problem with remote debugging in VS 2003 -- visual studio .net debugging

visual studio .net debugging : Problem with remote debugging in VS 2003

Roy Chastain
5/26/2006 1:32:39 PM

I am running on an XP SP2 system with full VS 2003 Enterprise installed.
I have a 2003 Enterprise R2 installed with the remote debugging (both native and managed) installed from the 2003 Enterprise CD.

Both machines are in the same domain.
The server is a member server for testing applications.
I am an administrator on both machines.
I have added my name to the Debug Account list in both the Local Policy on both machines and to the Default Domain Policy
I have done GPUpdate /force on both machines
I have restarted both machines

I receive the following error when I try to attach to a process on the 2003 server system
Unable to attach to the process. Attaching to processes in other users sessions is not allowed. Administrators can enable this
feature. Consult the help for more information.

There are no errors or warning in the event logs on either system.

Where do I go next?
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.

jetan NO[at]SPAM online.microsoft.com (
5/29/2006 12:00:00 AM

Hi Roy,

Thanks for your post!

Do you run the target process under the same account as the account you run
the XP SP2 debugger? There are some known security issues when you are
doing cross-accounts remote debugging, please refer to the 2 articles below:
"Remote Debugging Under Another User Account"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
l/vxtskRemoteDebuggingAcrossMachineAccounts.asp
"Unable to Attach to the Process"
http://msdn2.microsoft.com/en-US/library/h1cddsb5.aspx

To resolve this problem, you may set
HKLM\Software\Microsoft\MachineDebugManager\AllowLaunchAsOtherUser to 1 and
give it a retry.

Hope this helps!

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Roy Chastain
6/2/2006 12:00:00 AM

Jeffery,
Sorry about the delay in response. I got buried with other stuff and forgot this issue.
Yes, I am logging in on both systems with the same domain level account and I am running the debugged application from a command
line.

I added the reg value you gave me below and rebooted. Now it works.

THANKS

[quoted text, click to view]
-------------------------------------------
Roy Chastain
KMSYS Worldwide, Inc.

jetan NO[at]SPAM online.microsoft.com (
6/5/2006 1:42:55 AM

You are welcome.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about visual studio .net debugging

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007

home · blog · groups

Questions? Comments? Contact the dn