Microsoft's article can completely solve the problem of Visual InterDev
You need to install Visual InterDev Server, on the second disk of Visual Studio 6.0
HOWTO: Configure your Web Server for Visual InterDev 6.0 Asp Debugging
-------------------------------------------------- ------------------------------
The Information in this Article Applies TO:
Microsoft Visual InterDev, Version 6.0
Microsoft Windows NT Server Version 4.0
Microsoft Windows NT Workstation Version 4.0
Microsoft Windows 2000
-------------------------------------------------- ------------------------------
Summary
This article describes the recommended steps to configure your Web server for remote and local Active Server Pages (ASP) script debugging for use with Visual InterDev 6.0 There are four basic things that you must do.:
Install Debugging Components on The Web Server.
Add the nextary users to the administrators group of the web server.
Configure DCOM Permissions on The Web Server.
SET UP A Visual InterDev 6.0 Project for Debugging.
More information
Install / Confirm Debugging Components on The Web Server
Install or EnSure That You are Running The Following Components:
Microsoft Personal Web Server 4.0 or Internet Information Server 4.0 or Later.
Asp.dll Version 4.02.0662 or later. If you have version 4.02.0662, The File Size Must BE 330, 448 BYTES. You can install an upded version of ask.dll by Applying Windows NT Service Pack 4 or Later.
You May Have to Stop Web Services Before ASP.DLL TO GET Updated. From A Command Prompt, You Can Type The Following to Stop The Web Services:
Net Stop Iisadmin / Y
Microsoft FrontPage Server Extensions Version 3.0.2.1706 or Later.
The Microsoft Visual InterDev Server components. If you do not see this listed in the Add / Remove Programs utility in Control Panel, you can install it by running Setup.exe from the VID_SS directory on Visual Studio CD-ROM 2 or on CD-ROM 1 of the Visual InterDev Standalone Version.Remote Machine Debugger Components (Recommended).
IF you do not see this listed in Add / Remove Programs, you can install it by running setup.exe from the Scrpt_ss Directory on Visual Studio Disc 2 Or On Disc 1 of the Visual InterDev Standalone Version.
Visual Studio Service Pack 3 or Later, if you are running Windows 2000.
You Can Download Visual Studio Service Pack 3 from the Following Location:
Http://msdn.microsoft.com/vstudio/sp/vs6sp3/default.asp
NOTE: The Web Server Must Be A Windows NT 4.0 Workstation / Server OR A Windows 2000 Professional / Server / Advanced Server Computer.
Add The nextary users to the local administrators group of the web server
In Order to Correctly Use Debugging, You Must Be Part of The Local Administrators Group on The Web Server You Will Be Debugging Against.
Steps to Add Users to the Administrators Group in Windows NT 4.0:
From the start menu, select run.
TYPE: USRMGR Computer Name and Click OK.
Double-Click The Administrators Group in The Bottom Pane.
Add to debug.
Steps to add users to the administrators group in Windows 2000:
From The Start Menu, Select Programs, And The Select Administrative Tools.
From The Administrative Tools Menu, SELECT Computer Management.
Expand Local Users and Groups Under System Tools.
Select the groups folder.
Double-Click The Administrators Group in The Right Pane.
Add to debug.
Configure DCOM Permissions on the Web ServerFrom The Start Menu, SELECT RUN.
Type DCNFG.EXE and Click OK.
On The Applications Tab, Scroll Down To The Catalog Class and Double-Click It To View Properties.
Select the security tab.
Click Use Custom Access Permissions and The Click Edit.
Add The Users That You Will Allow To Debug To this List, Granting The ALOW Access Rights, or Simply Add The Administrators Group To this list.
Select The USE Custom Launch Permissions Option and Click Edit.
Add The Users That You Will Allow To Debug To this List, Granting The Mount Launch Rights, or Simply Add The Administrators Group To this list.
Select the Identity Tab.
Select The Interactive User Option.
Click Apply and the Click OK.
Display The Properties for the Machine Debug Manager, And Repeat Steps 4-11 for the Machine Debug Manager.
Close The DCOM Permissions Dialog Box and reboot your computer.
NOTE: The Following Are The Minimum Recommended Accounts That Should Be in Your DCOM Permissions for Both The Catalog Class and The Machine Debug Manager: Administrators, System, and Interactive.
SET UP A Visual InterDev 6.0 Project for Debugging
Create a New Web Project in Visual InterDev 6.0.
Add an asp page to the project.
Add The Following Lines of Code to the New ASP Page With Html Body:
<%
Response.write "Hello World"
%>
Right-Click On The Response.write Line and Select Insert Breakpoint. This Will Set A Breakpoint for That Line, And a Large Red Dot Will Appear To The Left of The Line In The Border.
Right-Click on The File in The Project Explorer and SET AS START PAGE.
From the debug menu, select start.
A dialog box should appear asking if you would like to enable ASP debugging on this project. Select yes.You will then be prompted for debugging credentials. Use one of the accounts that you added to the Administrators group.
The Debugger Should Break on Your Breakpoint, and the line shouth.
Note: IF Remote Debugging, The Client Is Required To Have Personal Web Server 4.0 or Later Installed. ASP Debugging is not supported on a windows 95 or windows 98 client.
References
Please See the Following Microsoft Knowledge Base Article for a list of related debugging articles:
Q244272 Visual InterDev 6.0 Debugging Resources
Additional Query Words:
Keywords: kbdebug kbide kbntos kbwinos2000 kbvisid600 kbgrpasp
Version: Windows: 6.0; Winnt: 4.0
Platform: Windows Winnt
Issue Type: Kbhowto
TECHNOLOGY: KBVCSEARCH
