PRB: Visual InterDev Debugger Stops Working After a Few Debugging Sessions (254244)


The information in this article applies to:

  • Microsoft Visual InterDev 6.0
  • Microsoft Internet Information Server 4.0
  • Microsoft Personal Web Server 4.0 for NT Workstation version 4.0
This article was previously published under Q254244

SYMPTOMS

After you successfully debug Active Server Pages (ASP) pages for a few debugging sessions, you may receive the error message
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?
or the debugger might stop breaking on breakpoints.

CAUSE

The packages that Visual InterDev creates in Microsoft Transaction Server on the Web server are created but never destroyed, and the identity of the packages is set to the user "Y". This is because the IWAM_Servername is not synchronized between the usermanager and the Internet Information Server (IIS) metabase.

RESOLUTION

To resolve this problem, resynch the IWAM_Servername's password between the usermanager and the IIS metabase. To do so, follow the instructions provided in the following Microsoft Knowledge Base article:

195956 Cannot Set AppRoot OutProc, MTS Package Identity Set to 'Y'

STATUS

This behavior is by design.

REFERENCES

For additional information, 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:5/29/2003
Keywords:kbBug kbDebug kbprb KB254244
©2002 Microsoft Corporation. All rights reserved.