Problem attaching script debugger to ASP under IIS6

Hi!

I've got a problem attaching the Script Debugger to ASP
pages under IIS6. Set up everything following IIS6
documentation: turned on ASP debug in IIS Manager; edited
permissions for Machine Debug Manager in the DCOM
configuration, giving Launch and Activate permissions to
Network Service (which is the account for the
corresponding process pool).

IIS is in WP isolation mode. ASP is activated. Sending
detailed error info to the browser is activated and works
fine. No errors in event log about DCOM app attach
permission denials.

Any ideas? How to make the Microsoft Script Debugger work with server-side
ASP (or Visual InterDev, or Office Script Editor for that matter)?

Thanks, Andrew

Hi Andrew,

From my view, the Script debugger is old, I'd suggest you could use the
VS.net IDE as the ASP script debugger. There is one article from
Gotdotnet.com introducing how to do so.
How to debug script in Visual Studio .NET
http://gotdotnet.com/team/csharp/learn/whitepapers/How%20to%20debug%20script
%20in%20Visual%20Studio%20.Net.doc

Based on my experience, there are two notes for the ASP debugging:
1. you will need to place your ASP pages in the default web site(port 80),
then we can use VS.net to attach the w3wp.exe process running the ASP and
debugging the pages.

2. Network Service account is designed as the default account for anonymous
internet user so it has very little permission. For performing the
debugging, please set your default web site worker process using the SYSTEM
as the identity. If using network service, we will need to grant it very
high permission which will affect your anonymous web site and generate
security hole at the server.

Please feel free to let me know if you have any question. It is my pleasure
to be of any assistance.

Best Regards,
Wei-Dong XU
Microsoft Product Support Services
This posting is provided "AS IS" with no warranties, and confers no rights.