A Windows Server 2008-based server that is running the Terminal Server role reports a Stop error when you control a session remotely from inside a session that is already being controlled remotely: "0x00000050"
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You start a Remote Desktop session on a Windows Server 2008-based server that is running the Terminal Server role.
You use the Terminal Services Manager snap-in to select the session that you want to control remotely.
From inside this remote-controlled session, you try to control another session remotely on the same server or on a different server. (This process is known as a double-hop.)
In this scenario, the Windows Server 2008-based server that you first connected to crashes and reports Stop error 0x00000050.
This problem was first corrected in Windows Server 2008 Service Pack 2.To resolve this problem, obtain the latest service pack for Windows Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
To prevent this problem, do not try to control a session remotely from inside a session that you are already controlling remotely.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you try to perform this kind of double-hop remote control from a Windows Server 2003-based terminal server, you receive error 87 in the user interface. However, the terminal server does not crash.