User Global Object Is Mistakenly Created As a System Global Object

This article was previously published under Q216254
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
When you develop an application to run under Windows NT Server 4.0, Terminal Server Edition, a call to an OLE object creation may cause any subsequent named objects to be created in the system global namespace rather than the namespace of the user.
RESOLUTION
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

STATUS
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.
4.00 wts tse
Properties

Article ID: 216254 - Last Review: 10/14/2013 15:40:42 - Revision: 2.2

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB216254
Feedback