You can ignore this message. Just click 'yes' and continue.

To set up the debugger in Visual InterDev, open IIS and right click on 
your website. Select properties from the context menu. At the bottom of 
the dialog box is a dropdown box named Applications Protection. Select 
High (Isolated). I have never used the middle choice so I don't know if it 
works for the debugger.

Then click the configuration button and select the App Debugging tab. 
Select both checkboxes under Debugging Flags. Then make sure you click on 
the OK button all the way out.

Inside of Visual InterDev right click on the page you want to debug and 
select it as the start page. Then use the start arrow on the tool bar at 
the top.

It will take a few seconds but you should get one or two error messages. 
Just click yes or OK and continue. You should be able to debug now, 
although it is a little tricky.
I was told that you had to run your website in local mode in order to 
debug but I have been able to debug just fine in master mode.

Also, if the page you select as the start page expects parameters from a 
previous page, you will have to supply them manually.

Hope this helps.

Tarey

> On my Windows 2000 Advanced Server I installed Visual InterDev 6.0 to 
edit 
> ASP codes and also updated SP 5 for VI and FrontPage Server Extensions 
> 2002, but I still get the following error when I debug the code:
> 
> Unabled to set server into correct debugging state automatically. You  
may 
> not be able to debug ASP pages. Do you want to continue launching the 
> debugger?
> 
> How can I configure the system further to resolve the error? Thank a lot!