This article was previously published under Q318717
This article has been archived. It is offered "as is" and will no longer be updated.
If you have not performed any debugging on your computer with either Visual Studio .NET or the Visual C++ 6.0 Debugger, remote RPC debugging does not work, even though you have turned on RPC Debugging in VS .NET.
Visual Studio .NET sets the registry key DebugObjectRPCEnabled, which permits RPC debugging on the computer. However, Visual Studio .NET does not set the registry key when you click to select RPC Debugging. Visual Studio .NET sets the registry key the first time you perform step-by-step debugging on your computer.
Run a debug session and do step-by-step debugging at least one time before you use the RPC debugging on your computer.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This issue may occur in the following test scenario:
Client and server applications are developed on one computer.
While you are testing the applications by using two computers, you find an issue and you have to use remote RPC debugging.
You install Visual Studio .NET on the second computer.
You set RPC Debugging in Visual Studio .NET on the second computer. To do this, you follow these steps:
In Visual Studio .NET, on the Options menu, click Debugging. The RPC Debugging option is in the Native subsection.
Click to select RPC Debugging to set the registry key DebugObjectRPCEnabled.
However, the registry key is not actually set until the first time you run step-by-step debugging on your computer.
The full path of the registry key is as follows:
For Windows NT, Windows 2000, and Windows XP:
HKEY_LOCAL_MACHINE\Software\ Microsoft\ Windows NT\ CurrentVersion\ DebugObjectRPCEnabled
For Windows 95, Windows 98, and Windows Millennium Edition (Windows Me):