I have a similar problem. Based on what showed up in the event log, it 
appears to be related to the fact that I didn't install the script 
debugger in the default installation directory. (I haven't tried Peter's 
server side fix yet, but it looks interesting.)

Although I haven't had time to test installing into a different directory, 
I did cobble together a work around.  I have a small batch file that 
changes into the script debugger directory and starts the debugger 
running. I minimize that window and then run IE and then can properly 
debug my scripts.

Here's my batch file:

-----------------------------------
E:
cd "\program files"
cd "microsoft script debugger"
start msscrdbg.exe -Embedding
-----------------------------------

If you're using NT or W2K you can leave the quotes off the directory names.

Good luck!

JR

> Here's what I have done in NT4.0 to get ASP debugging working.  Not sure 
how
> different it is in 2k.
> 
> In Interdev, turn on "Automatically enable ASP server-side script 
debugging
> on  launch" on the Launch tab of your web project properties.
> In IIS manager, go to your virtual directory properties, click on the 
home
> directory tab, then the Configuration... button.
> From here, you can go to the App Debugging tab, and turn on the two debug
> flags. Ok everything back out to the main IIS window, and STOP and 
RESTART
> the web services. You may need to do "net stop iisadmin /y" from a 
command
> line to make it work. I have had problems using just the IIS manager.
> In Interdev, right-click the file you want to debug, and select "Set as
> start page"
> Then hit the play (right arrow) button in Interdev. This will open up a 
new
> IE window, and will load the page.  Then go into Interdev and set a
> breakpoint (or just make a line of bad code ;) and refresh the IE window.
> This SHOULD - in theory - send you into Interdev at the breakpoint or 
error.
> You can then step through the file with F11 to go line by line.
> 
> Try that out and see if it works. You might have to fiddle with stopping 
and
> starting the web services to make it work. It's very specific.  I spent 
30
> minutes yesterday trying to shut it OFF.
> 
> Good luck.
> 
> Peter L
> 
> -----Original Message-----
> From: Peter Tibbott [mailto:peter_tibbott@b...]
> Sent: Tuesday, February 13, 2001 12:55 AM
> To: Interdev_Programming
> Subject: Problem with MS Script Debugger
> 
> 
> Hi, am using VI as my page editor, running on W2000, have created a 
virtual
> dir for the debugging tutorial from Chap 9. and changed the App 
Debugging to
> Enable ASP server-side script debugging.
> 
> I've typed in the buggy ASP and opened it successfully in IE
> (http://127.0.0.1/Debugging/Debug.asp).
> 
> I can't get the debugger to open from IE5.5 (View\Script 
Debugger\Open)...
> When I run it from the Start Menu (\Accessories\Microsoft Script
> Debugger\Microsoft Script Debugger), I don't see any Running Documents - 
not
> even 'Microsoft Internet Explorer'.  I've hit the refresh button so many
> times I'm in danger of wearing it out!
> 
> I don't want to have to use the Debugger, but in reality I know sooner or
> later I'll need it.
> 
> What's the foolish mishtake(sic) that I'm making?
> 
> Thanks in advance, Pete.
>