Solved

Visual Studio 2005 cannot "Attach to Process" for IIS for remote debugging

Posted on 2009-05-05
8
1,243 Views
Last Modified: 2013-11-26
I am trying to perform remote debugging using Visual Studio 2005.

Visual Studio Remote Debugging Monitor starts successfully on the remote computer (the one with IIS).  I run it remotely from my local computer.
It gives me a server name which I assume is a virtual server of the form DOMAINNAME\username@LOCALCOMPUTERNAME.
In Visual Studio, I load my classic ASP file, the click on Debug - Attach To Process.
I enter the above virtual server name as qualifier.  I make sure both "Show processes for all users" and "Show processes in all sessions" are checked.

All of the instructions I have found at MSDN and other places tell me that I should be able to select w3wp.exe (the IIS 6 process on the remote server) and then perform debugging.

Unfortunately, the w3wp.exe process is not listed.  In fact, the processes listed appear to be the ones on my LOCAL computer.

Can someone tell me why I am not seeing the necessary process?

I have administrative permissions on both machines and am in the group "debugger users".  There is no firewall between the machines.

(An attempt to use the Remote Debugger Configuration Wizard to "run as service" resulted in successful configuration but failed due to invalid logon, so I am trying to make the manual connection work.)
0
Comment
Question by:netsmithcentral
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 96

Expert Comment

by:Bob Learned
ID: 24314620
You didn't mention whether you changed the "Qualifier" to the remote machine name, to see the processes on that machine...


Attach-to-Process.png
0
 
LVL 12

Author Comment

by:netsmithcentral
ID: 24314862
It is supposed to work with the "virtual server" name supplied by the Remote Debugger Monitor.
However, yes, I did try using the name of the remote IIS server and received an error message that the remote debugger monitor was not running on that machine.
0
 
LVL 12

Author Comment

by:netsmithcentral
ID: 24314885
Additional comment:  I know the "virtual server" name is supposed to work as the Qualifier because this gives the ability for multiple simultaneous debugging session, each run off a different virtual server.  I have found documentation to the at effect.
0
MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

 
LVL 96

Expert Comment

by:Bob Learned
ID: 24314973
Have you read anything about the remote debugger monitor (msvsmon.exe)?

How to: Set Up Remote Debugging
http://msdn.microsoft.com/en-us/library/bt727f1t.aspx

"To enable remote debugging, you can do one of two things:

   -- Install the Remote Debugging Monitor (msvsmon.exe) on the remote computer and start it when you begin debugging.

   -- Run the Remote Debugging Monitor remotely from a share."
0
 
LVL 12

Author Comment

by:netsmithcentral
ID: 24355992
I have read everything I can find about the remote debugger.  I have employed both the methods described by TheLearnedOne but it is simply NOT working as advertised.  Which is why we post.
0
 
LVL 96

Expert Comment

by:Bob Learned
ID: 24357472
"it is simply NOT working as advertised" only begins to describe your problem.  Are you saying that you got msvsmon.exe up and running on the remote machine, and still can't attach to the process?
0
 
LVL 12

Author Comment

by:netsmithcentral
ID: 24359647
Yes.
0
 
LVL 12

Accepted Solution

by:
netsmithcentral earned 0 total points
ID: 24366155
Well, I am withdrawing this question.  Apparently due to modifications to the operating system, specifically for WinXP, remote debugging is no longer possible for classic ASP in Visual Studio 2005.  I installed Visual Studio 2005 on the IIS server machine and access it via Remote Desktop Connection for "local" debugging.
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In my previous two articles we discussed Binary Serialization (http://www.experts-exchange.com/A_4362.html) and XML Serialization (http://www.experts-exchange.com/A_4425.html). In this article we will try to know more about SOAP (Simple Object Acces…
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question