Microsoft KB Archive/183657

= Unable to Insert OLE Objects into Application Documents =

Article ID: 183657

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition
 * Microsoft Windows NT Server 4.0 Enterprise Edition

-



This article was previously published under Q183657



SYMPTOMS
When inserting an OLE object into an application document, you may receive one of the following error messages:

Cannot create object

-or-

Cannot create OLE object

-or-

Operation caused OLE error 36

-or-

Failed to create OLE object

-or-

OLE object problem

This symptom has occurred in OLE applications such as Serif PagePlus 3.0, Adobe PageMaker 5.0, and Harvard Graphics 3.



CAUSE
The application is sending a WM_DDE_INITIATE message that is never acknowledged by the OLE application server.

-or-

Under certain conditions broadcast messages can become blocked. This will only occur when OLE threads are open but those threads are not processing messages.



RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft 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 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.



MORE INFORMATION
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: hang oleapp link embed insert

Keywords: kbbug kbfix KB183657

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.