"Roel Korsten" <no_spam> wrote in message
news:%23v4kv8PuFHA.904@tk2msftngp13.phx.gbl...
> Hi all,
>
> I know there are plenty of posts about remote debugging with vs 2003 but I
> can't make things work no matter what I've read or done so far :(
>
> The VS2003 is installed in a winXP Pro SP2 pc (firewall disabled) and the
> IIS 6 is running on a remote win2003 Server pc (with all updates installed
> and no firewall what so ever).
>
> The error message is: "Error while trying to run project: Unable to start
> debugging on the web server. The debugger component on the server failed
> to connect to the local machine."
>
> I've tried everything mentioned in various KB articles and newsgroups but
> no
> luck.
>
> Anyone ?
>
> Roel Korsten
>
>

"Jim" <please.reply@group> wrote in message
news:eF8BBKguFHA.3932@TK2MSFTNGP15.phx.gbl...
> Roel,
> I feel your pain. I've recently been there. I scoured newsgroups, MSDN,
> ...
> Below are the steps I took to get remote debugging working between VS.NET
> 2003 Win XP SP2 station and a .NET application running in IIS on Windows
> Server 2003 (SP1, I think).
> I'm still not sure if the next to the last step is a good idea,
> security-wise.
> (9. Under 'Permissions for ANONYMOUS LOGON' select the 'Remote
> Access' box. Click OK.)
> Lots of luck!
> Jim
>
> I. Configure the Windows Server
> A. Setting Up Remote Debugging (
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vctskinstallingremotedebugmonitor.asp )
>
>
> 1. Use "preferred method" that employs DCOM and Machine Debug
> Manager.
> 2. Use "Full Remote Debugging" instead of "Native Remote Debugging".
>
>
> B. ASP Remote Debugging Setup (
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskaspremotedebuggingsetup.asp )
> 1. Added this key:
> a)
> [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{6EB22881-8A19-11D0-81B6-00A0C9231C29}]
> b) @="Catalog Class"
> c) "DllSurrogate"=""
>
>
> 2. This key already present:
> a)
> [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6EB22881-8A19-11D0-81B6-00A0C9231C29}]
> b) @="Catalog Class"
> c) Added: "AppID"="{6EB22881-8A19-11D0-81B6-00A0C9231C29}"
>
>
> C. Adding Debugger Users and Configuring DCOM (
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/html/vxtskinstallingdcom.asp )
>
>
> II. Configure the Workstation Running Visual Studio .NET
> A. This may vary from workstation to workstation. Following are some
> suggestions. Good luck!
>
>
> B. Create a simple .NET application on the remote server for
> trying/testing remote debugging:
> 1. HOW TO: Set Up and Use Remote Debugging in Microsoft Visual
> Studio .NET ( http://support.microsoft.com/kb/318041 )
> C. In IIS Manager on genome-mars, open properties for the web being
> debugged. The web being debugged must be named. Also, 'Integrated
> Windows authentication' must be enabled for the web.
> D. Run DebuggerFirewall utility on workstation:
> E. Description of the DebuggerFirewall utility that makes the Visual
> Studio Remote Debugger work through the Windows XP Service Pack 2 firewall
> (http://support.microsoft.com/?id=841177 )
> F. In IE, add http://mars.genome.uab.edu (or the base URL associated
> with your project) to trusted sites.
> G. (IEàToolsàInternet Options.àSecurityàTrusted sitesàSites.)
> H. Verify your membership in the 'Debugger Users' group on the server.
> I. Enable 'Integrated Windows Authentication' for the web to be
> debugged.
> J. Verify that ASP.NET debugging is enabled in project properties.
> K. Right click on 'Default Web Site' in IIS on Genome-Mars, select
> properties, and ensure that 'Enable HTTP Keep-Alives' is selected.
> L. On workstation running Visual Studio .NET, take the following
> steps. (This advice came from http://support.microsoft.com/kb/833977/ ,
> which refers to debugging in Windows XP SP2, but it has been known enable
> remote debugging between VS.NET on a XP SP2 workstation and IIS on a
> Windows Server 2003.)
> 1. Run 'dcomcnfg'.
> 2. Expand 'Component Services'.
> 3. Expand 'Computers'.
> 4. Click on 'My Computer'.
> 5. On the main menu, click on the 'Configure my Computer' button.
> 6. The 'My Computer' dialog box appears. Select the 'COM Security'
> tab.
> 7. Under 'Access Permissions', click on the 'Edit Limits.' button.
> 8. Under 'Group or user names:' select 'ANONYMOUS LOGON'.
> 9. Under 'Permissions for ANONYMOUS LOGON' select the 'Remote Access'
> box. Click OK.
> 10. A restart may be required to activate this settings change.
>
>
>
>
> "Roel Korsten" <no_spam> wrote in message
> news:%23v4kv8PuFHA.904@tk2msftngp13.phx.gbl...
>> Hi all,
>>
>> I know there are plenty of posts about remote debugging with vs 2003 but
>> I can't make things work no matter what I've read or done so far :(
>>
>> The VS2003 is installed in a winXP Pro SP2 pc (firewall disabled) and the
>> IIS 6 is running on a remote win2003 Server pc (with all updates
>> installed and no firewall what so ever).
>>
>> The error message is: "Error while trying to run project: Unable to start
>> debugging on the web server. The debugger component on the server failed
>> to connect to the local machine."
>>
>> I've tried everything mentioned in various KB articles and newsgroups but
>> no
>> luck.
>>
>> Anyone ?
>>
>> Roel Korsten
>>
>>
>
>

> Thanx Jim,
>
> I'll try all of them.
>
> Greetings,
> Roel
>
>
> "Jim" <please.reply@group> wrote in message
> news:eF8BBKguFHA.3932@TK2MSFTNGP15.phx.gbl...
> > Roel,
> > I feel your pain. I've recently been there. I scoured newsgroups, MSD=
N,
> > ...
> > Below are the steps I took to get remote debugging working between VS.N=
ET
> > 2003 Win XP SP2 station and a .NET application running in IIS on Windows
> > Server 2003 (SP1, I think).
> > I'm still not sure if the next to the last step is a good idea,
> > security-wise.
> > (9. Under 'Permissions for ANONYMOUS LOGON' select the 'Remote
> > Access' box. Click OK.)
> > Lots of luck!
> > Jim
> >
> > I. Configure the Windows Server
> > A. Setting Up Remote Debugging (
> > http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/vsde=
bug/html/vctskinstallingremotedebugmonitor.asp )
> >
> >
> > 1. Use "preferred method" that employs DCOM and Machine Debug
> > Manager.
> > 2. Use "Full Remote Debugging" instead of "Native Remote Debugging=
"=2E
> >
> >
> > B. ASP Remote Debugging Setup (
> > http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/vsde=
bug/html/vxtskaspremotedebuggingsetup.asp )
> > 1. Added this key:
> > a)
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{6EB22881-8A19-11D0-81B6-00A=
0C9231C29}]
> > b) @=3D"Catalog Class"
> > c) "DllSurrogate"=3D""
> >
> >
> > 2. This key already present:
> > a)
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6EB22881-8A19-11D0-81B6-00A=
0C9231C29}]
> > b) @=3D"Catalog Class"
> > c) Added: "AppID"=3D"{6EB22881-8A19-11D0-81B6-00A0C9231C29}"
> >
> >
> > C. Adding Debugger Users and Configuring DCOM (
> > http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/vsde=
bug/html/vxtskinstallingdcom.asp )
> >
> >
> > II. Configure the Workstation Running Visual Studio .NET
> > A. This may vary from workstation to workstation. Following are so=
me
> > suggestions. Good luck!
> >
> >
> > B. Create a simple .NET application on the remote server for
> > trying/testing remote debugging:
> > 1. HOW TO: Set Up and Use Remote Debugging in Microsoft Visual
> > Studio .NET ( http://support.microsoft.com/kb/318041 )
> > C. In IIS Manager on genome-mars, open properties for the web being
> > debugged. The web being debugged must be named. Also, 'Integrated
> > Windows authentication' must be enabled for the web.
> > D. Run DebuggerFirewall utility on workstation:
> > E. Description of the DebuggerFirewall utility that makes the Visual
> > Studio Remote Debugger work through the Windows XP Service Pack 2 firew=
all
> > (http://support.microsoft.com/?id=3D841177 )
> > F. In IE, add http://mars.genome.uab.edu (or the base URL associated
> > with your project) to trusted sites.
> > G. (IE=E0Tools=E0Internet Options.=E0Security=E0Trusted sites=E0Site=
s=2E)
> > H. Verify your membership in the 'Debugger Users' group on the serv=
er.
> > I. Enable 'Integrated Windows Authentication' for the web to be
> > debugged.
> > J. Verify that ASP.NET debugging is enabled in project properties.
> > K. Right click on 'Default Web Site' in IIS on Genome-Mars, select
> > properties, and ensure that 'Enable HTTP Keep-Alives' is selected.
> > L. On workstation running Visual Studio .NET, take the following
> > steps. (This advice came from http://support.microsoft.com/kb/833977/ ,
> > which refers to debugging in Windows XP SP2, but it has been known enab=
le
> > remote debugging between VS.NET on a XP SP2 workstation and IIS on a
> > Windows Server 2003.)
> > 1. Run 'dcomcnfg'.
> > 2. Expand 'Component Services'.
> > 3. Expand 'Computers'.
> > 4. Click on 'My Computer'.
> > 5. On the main menu, click on the 'Configure my Computer' button.
> > 6. The 'My Computer' dialog box appears. Select the 'COM Security'
> > tab.
> > 7. Under 'Access Permissions', click on the 'Edit Limits.' button.
> > 8. Under 'Group or user names:' select 'ANONYMOUS LOGON'.
> > 9. Under 'Permissions for ANONYMOUS LOGON' select the 'Remote Acce=
ss'
> > box. Click OK.
> > 10. A restart may be required to activate this settings change.
> >
> >
> >
> >
> > "Roel Korsten" <no_spam> wrote in message
> > news:%23v4kv8PuFHA.904@tk2msftngp13.phx.gbl...
> >> Hi all,
> >>
> >> I know there are plenty of posts about remote debugging with vs 2003 b=
ut
> >> I can't make things work no matter what I've read or done so far :(
> >>
> >> The VS2003 is installed in a winXP Pro SP2 pc (firewall disabled) and =
the
> >> IIS 6 is running on a remote win2003 Server pc (with all updates
> >> installed and no firewall what so ever).
> >>
> >> The error message is: "Error while trying to run project: Unable to st=
art
> >> debugging on the web server. The debugger component on the server fail=
ed
> >> to connect to the local machine."
> >>
> >> I've tried everything mentioned in various KB articles and newsgroups =
but
> >> no
> >> luck.
> >>
> >> Anyone ?
> >>
> >> Roel Korsten
> >>
> >>
> >
> >