RE: The debugger component on the server failed to connect to the

Never mind of my last reply. It worked!!!

For step three, I found that I have to go to property on My Computer and
then I was able to do step4 to step7.

Thank you for pointing me to the right direction.
Jim

""Jeffrey Tan[MSFT]"" wrote:

Hi Jim,

What version of Windows are you experiencing this issue?
Can you try to open the "Output" window in the VS.net2003 IDE? Is there any
additional error message displayed there? I assume there is one message
stating:
"And also the following message appears in the debugging output: Auto
attach to process "<pid> w3wp.exe" on machine "Server name" failed. Error
code 0x800405a4."

You may follow the section from <http://support.microsoft.com/?id=833977>
shown below to resolve this problem.

Configure DCOM on the computer that is running Visual Studio .NET
Note After you make changes by using the Distributed Component Object Model
Configuration utility (Dcomcnfg.exe), you must restart your computer for
the changes to take effect.

1. At a command prompt, type dcomcnfg, and then press ENTER. Component
Services opens.
2. In Component Services, expand Component Services, expand Computers, and
then expand My Computer.
3. On the toolbar, click the Configure My Computer button. The My Computer
dialog box appears.
4. In the My Computer dialog box, click the COM Security tab.
5. Under Access Permission, click Edit Limits. The Access Permission dialog
box appears.
6. Under Group or user names, click ANONYMOUS LOGON.
7. Under Permissions for ANONYMOUS LOGON, select the Remote Access check
box, and then click OK.

Please give it a try and let me know the result. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.