ID: Q178926
The information in this article applies to:
When attempting to receive messages sent to a public local queue on a independent client, all ActiveX clients stop responding while offline when invoking the "open" method.
NOTE: Eventually the network call times out and control is returned to the client application. At that point, it works as expected. This time out varies from two to ten minutes.
When the "open" method is invoked, the ActiveX object attempts to query the queue properties from the site controller, and not the local data store.
This problem has been fixed in the Windows NT Option Pack version of Microsoft Message Queue Server (MSMQ). You can resolve this problem by downloading this version and upgrading all independent clients to this version. You can find this version of MSMQ at:
http://www.microsoft.com/ntserver/guide/whatisntop.asp
Although upgrading to the Windows NT Option Pack version of MSMQ is
recommended, a workaround is to use private queues, because private queues
do not suffer from this problem. Private queue information exists only on
the local hard disk drive in the Msmq\Storage\Lqs directory, not on the
site controller.
For more information on using the MSMQ ActiveX objects, refer to the SDK online documentation.
Additional query words: active x hang hung freeze frozen lock locked up
Keywords : kbusage MQQueue
Version : WINNT:1.0
Platform : winnt
Hardware : ALPHA x86
Issue type : kbprb
Solution Type : kbfix
Last Reviewed: January 7, 1998