Last post Apr 10, 2007 11:35 AM by pblecha
Apr 02, 2007 03:28 PM|pblecha|LINK
I'm trying to set up debugging with a remote production server and ASP.net 1.1 applications. I'm at a mid-sized company; consequently, my local server and the production server are on different domains. I've been unable in the past to use Visual Studio
2003 to debug applications on the production server because of a series of permissions issues, and other issues. I actually migrated one application to the 2.0 version and VS2005, but debugging turned out not to be any easier because of the domain/permissions
My local machine is Windows XP SP2; the remote server is WS2003. I would greatly appreciate a walkthrough explanation of how to deploy an application and then hook up my local copy of VS2003 to the remote application for debugging.
Debug asp.net web application
Visual Studio 2003
Apr 02, 2007 04:33 PMemail@example.com|LINK
You've hit most of your issue with the multiple domains and permissions. The basics are that the user doing the debugging has to be a member of the debuggers group on the server being debugged, and that the domain of the server has to trust the domain of
the user to allow that user access.
Apr 09, 2007 12:34 PM|pblecha|LINK
Apr 10, 2007 11:35 AM|pblecha|LINK
I believe I have correctly set permissions for both workstation and server; I have opened the ports on both sides for remote procedure calls; and I have set both sides to see the other as a trusted site. Here is the error I continue to get:
Error while trying to run project: Unable to start debugging on the web server. The remote procedure call failed and did not execute.
I've been over and over the KB articles on MS; I feel that they are missing something. What are some other things to check?