Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Debugging / June 2008

Tip: Looking for answers? Try searching our database.

Visual Studio 2003 remote debugging

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark - 20 Jun 2008 17:46 GMT
I am setting up my new laptop and trying to put on a dual install of Visual
Studio 2003 and 2008. And have been successful with everything except for the
remote debugging in Visual Studio 2003.  I have 2003 remote debugging working
fine on my old laptop but when I open the same project on the same server
with the new one and try to debug it will not connect properly. If I try to
start in debug I get "Unable to start debugging on the web server. The
debugger component on the server failed to connect to the local machine". If
I run the project and try to connect to the w3wp.exe process on the server I
get the same error.

I have searched MSDN and the knowledgebase as well as googled and gone
through ever site with ever suggestion. I have set permissions, checked
dcomcnfg, reinstalled the remote components and lot of other failed remedies.
Any suggestions?
Evan Freeman - 20 Jun 2008 20:56 GMT
The asp.net account needs to have debugger permission sturned on, if not
thats usually the error you will get. Probably installing both on one
machine has a slight conflict.

Signature

Evan Freeman
Evan.E.Freeman@gmail.com
http://evanfreeman.blogspot.com

>I am setting up my new laptop and trying to put on a dual install of Visual
> Studio 2003 and 2008. And have been successful with everything except for
[quoted text clipped - 16 lines]
> remedies.
> Any suggestions?
Mark - 24 Jun 2008 15:26 GMT
Can you elaborate more? Since this is on a non production server I have given
administrator permissions to most everything in an attempt to make this work.
And the ASPNET user has been in the Debugger Users all along.

It works from my old install of VS2003 but not the new one where I have
VS2003 and VS2008 installed on.

> The asp.net account needs to have debugger permission sturned on, if not
> thats usually the error you will get. Probably installing both on one
[quoted text clipped - 20 lines]
> > remedies.
> > Any suggestions?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.