FIX: You Cannot Move Out of Remote Debug to the Client Computer by Pressing F5 (315945)


The information in this article applies to:

  • Microsoft Visual C++ Standard Edition, version 6.0
This article was previously published under Q315945

SYMPTOMS

When you do remote debugging on a DCOM server, and then you press F5 to return to the client computer, Visual Studio .NET stops responding (hangs).

CAUSE

This behavior occurs because the just-in-time (JIT) debugger on the remote computer does not have remote procedure call (RPC) debugging turned on.

RESOLUTION

To avoid this behavior, follow these steps:
  1. On the remote computer, start the Visual Studio IDE.
  2. On the Tools menu, click Options, click Debugging, and then click Native.
  3. Verify that RPC debugging is selected.

STATUS

This bug was corrected in Microsoft Visual C++ .NET 2002.

MORE INFORMATION

Steps to Reproduce the Behavior

On the server computer, do the following:
  1. Write an ATL out of process server named AtlServer; an interface method named method1 is created automatically.
  2. At a command prompt, run AtlServer.exe /regserver to register the ATL server.
  3. Start the Visual Studio .NET IDE.
  4. On the Tools menu, click Options. Click Debugging, and then click Native. Verify that RPC debugging is not selected.
On the client computer, do the following:
  1. Write the client, which has access to the interface method of AtlServer.
  2. Register AtlServer and its proxy DLL.
  3. Use the DCOMCNFG tool or the OLEVIEW tool to configure AtlServer to run on the server computer.
  4. In the Visual Studio .NET IDE, verify that RPC debugging is turned on.
  5. Debug the client until the method1 call, and then press F11 to step into the debugger.
  6. The Just-In-Time Debugging dialog box appears on the server computer. Click Yes to attach to the AtlServer process.
  7. Press F5; the IDE stops responding on both the server computer and the client computer.

REFERENCES

For additional information about how to configure the DCOM server and the client, click the article number below to view the article in the Microsoft Knowledge Base:

158582 HOWTO: Configure a Non-DCOM Server and Client to Use DCOM

Modification Type:MajorLast Reviewed:12/11/2003
Keywords:kbBug kbDebug kbpending KB315945 kbAudDeveloper
©2003 Microsoft Corporation. All rights reserved.