Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2009-05-05
8
Medium Priority
?
1,258 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
Basic Security of Your VPC

So, you’ve got this shiny new VPC and a fancy new application configured on your EC2 servers ready to go. This application is only accessible from your computer, which is great for security, but you need your users to be able to access it! So, what’s the easiest way to do this?

 
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

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

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

The object model of .Net can be overwhelming at times – so overwhelming that quite trivial tasks often take hours of research. In this case, the task at hand was to populate the datagrid from SQL Server database in Visual Studio 2008 Windows applica…
Today I had a very interesting conundrum that had to get solved quickly. Needless to say, it wasn't resolved quickly because when we needed it we were very rushed, but as soon as the conference call was over and I took a step back I saw the correct …
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …

721 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