PRB: Visual InterDev ASP Remote Debugging Fails from Windows NT 4.0 to Windows 2000 and from Windows 2000 to Windows NT 4.0 (258930)



The information in this article applies to:

  • Microsoft Visual InterDev 6.0

This article was previously published under Q258930

SYMPTOMS

When you automatically remote debug Active Server Pages (ASP) by using the Visual InterDev 6.0 debugger from a Windows NT 4.0 client to a Windows 2000 Web server, the following error message occurs:
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?
When you automatically debug ASP by using the Visual InterDev 6.0 debugger from a Windows 2000 client to a Windows NT 4.0 Web server, the following error message occurs:
Unable to automatically configure and launch remote debugging because of an incompatibility between version of Internet Information Server (IIS) on the client and the server. The usual cause for this error is attempting to debug ASP pages on an IIS4 server from a Windows 2000 client. In order to debug ASP pages, you should not continue launching the debugger. Instead, you should enable debugging manually on the server as described in the Troubleshooting topic of the Visual InterDev documentation.

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?

NOTE: If your client computer is a Windows 2000-based computer that does not have Service Pack 3 for Visual Studio installed, the following error message occurs:
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?

CAUSE

This behavior occurs because Visual InterDev uses the IIS Admin Service (IISAdmin) Active Directory Service Interfaces (ADSI) Provider to query the remote Web server. The IISAdmin ADSI Providers for Internet Information Server (IIS) 4.0 and Internet Information Services (IIS) 5.0 are not compatible.

RESOLUTION

To resolve this behavior, you need to manually attach the debugger.

For additional information about debugging from a Windows NT 4.0 client to a Windows 2000 Web server, please click the article number below to view the article in the Microsoft Knowledge Base:

258929 HOWTO: Debug ASP Applications Manually Against Windows 2000 Web Server

For additional information about debugging from a Windows 2000 client to a Windows NT 4.0 Web server, please click the article number below to view the article in the Microsoft Knowledge Base:

196378 HOWTO: Debug ASP Applications Manually Against Windows NT 4.0 Web Server

STATUS

This behavior is by design.

REFERENCES

For additional information about debugging, please click the article number below to view the article in the Microsoft Knowledge Base:

244272 INFO: Visual InterDev 6.0 Debugging Resources


Modification Type:MajorLast Reviewed:10/15/2002
Keywords:kbBug kbDebug kbDSupport kbprb KB258930