CoInitialize() May Cause OLE Applications to Stop Responding (159273)
The information in this article applies to:
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
This article was previously published under Q159273 SYMPTOMS
After a Windows OLE application (such as Date/Time in Control Panel) issues
a SendMessage(HWND_BRAODCAST) to a console application, the Windows OLE
application appears to stop responding.
CAUSE
The console application does not have a Windows message loop.
If a console application calls CoInitialize() to initialize the Component
Object Model (COM) library, it does not have a Windows message queue. This
causes OLE applications to stop responding while they are waiting for the
console application to process their messages. The basic assumption with
OLE is that OLE applications are Windows applications, and that they
process messages on a regular basis.
WORKAROUND
To work around this problem, do either of the following:
- Make sure your console application has an active Windows message loop.
-or-
- In Windows NT 4.0, instead of using CoIninitialize(), write your code to
call CoInitializeEx(NULL, COINIT_MULTITHREADED), which does not use
Windows messages for object remote procedure calls (RPCs).
| Modification Type: | Major | Last Reviewed: | 4/13/2004 |
|---|
| Keywords: | kbinterop kbnetwork kbprb KB159273 |
|---|
|