MORE INFORMATION
The following is a link to a comprehensive article on
Visual InterDev 6.0 debugging in the Microsoft Developer Network (MSDN) Online
Library:
The following is a link to a video presentation of debugging
Active Server Pages (ASP) manually:
For
additional information about debugging your Visual InterDev projects, click the
article numbers below to view the articles in the Microsoft Knowledge Base:
199004 INFO: VI6 ASP Debugging Not Supported in Windows 95/98
196378 HOWTO: Debug ASP Applications Manually Against Windows NT 4 Web Server
192011 HOWTO: Configure Your Web Server for Visual InterDev 6.0 ASP Debugging
237561 INFO: How to Read the Viddbg.exe Output
244373 INFO: Automatic Cross-Domain Debugging Not Supported in Visual InterDev 6.0
200998 HOWTO: Debug a Visual Basic DLL from Visual InterDev
258929 HOWTO: Debug ASP Applications Manually Against Windows 2000 Web Server
263658 HOWTO: Debug Remotely Using Visual InterDev on a Server with Site Server Personalization and Membership Configured
For additional information on resolving errors that you may
receive while debugging your Visual InterDev projects, click the article
numbers below to view the articles in the Microsoft Knowledge Base:
216668 PRB: VI Debugger Does Not Close Connections When Stopping Before Page Executes
HTTP Error 403
403.9
Access Forbidden: Too many users are connected
This error can be
caused if the Web server is busy and cannot process your request due to heavy
traffic. Please try to connect again later.
Please contact the Web
server's administrator if the problem persists.
242462 PRB: Unable to Find Server. Unable to Set Server Into Correct Debugging State Automatically
Unable to find server. Unable
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?
230507 PRB: Unable to Find Project on Web Server or to Set Server Into Correct Debugging State
Unable to find project on
server. Unable 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?
202040 PRB: Can't Attach to Application 'Microsoft Active Server Pages'
Can't attach to application
'Microsoft Active Server Pages (XXX)' on machine '<machinename>'. Do you
want to continue anyway?
194013 PRB: No Warning From VID Debugger if Connection to Server Fails
Internet Explorer cannot open
the Internet site 'http://mysite.com'.
A connection with the server
could not be established.
259063 PRB: Visual InterDev 6.0 Debugging Does Not Work After Upgrade to Windows 2000
Unable 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?
258930 PRB: Visual InterDev ASP Remote Debugging Fails from Windows NT 4.0 to Windows 2000 and from Windows 2000 to Windows NT 4.0
Unable to find server. Unable
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?
254244 PRB: Visual InterDev Debugger Stops Working After a Few Debugging Sessions
Unable 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?
251029 PRB: Visual InterDev Debugger 'Hangs' When Stopping
261305 PRB: Visual InterDev Debugger Skips Server-Side Break Points
224957 FIX: Cannot Debug HTC (IE 5 Script Behaviors) With VI 6.0
224937 FIX: HTA App (IE 5 Behaviors) Debugging Shuts Down IE 5
233035 BUG: Client-Side Breakpoints in Active Server Pages Not Hit with Internet Explorer 5 Installed
236094 BUG: Visual InterDev 6.0 Debugger Doesn't Process Client-Side Breakpoints When Using Response.Redirect
252895 PRB: VBScript 'Stop' Statement Does Not Start Script Debugger
269827 VBScript 'Stop' Statement in .wsc Components Does Not Start Script Debugger When Called from ASP
256197 PRB: Visual InterDev 6.0 ASP Debugging Fails Under Terminal Server
312880 BUG: Visual InterDev 6.0 ASP Debugging Does Not Function Properly on a Windows XP-Based Computer