This article was previously published under Q195612
This article has been archived. It is offered "as is" and will no longer be updated.
When developing an application to run under Windows Terminal Server, a callto the RpcServerUseProtseqEp() API may cause any subsequent named objectsto be created in the global name space versus the name space of the clientuser. Any Win32 API which creates names objects may be affected if calledfollowing a call to RpcServerUseProtseqEp().
For example, if a named pipes application were to create an event objectusing the CreateEvent() API following a call to the RpcServerUseProtseqEp()API, the event object would be created in the global name space instead ofthe preferred local name space of the Windows Terminal Server user. If thenamed object is created before calling the above offending RPC API, thenamed object is created in the correct user name space.
The problem is that the RcpServerUseProtSeqEp() API does not properlyrestore the user environment when returning from kernel mode.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.