BUG: Windows 95 Independent Clients May Hang When Sending Messages Offline

• Microsoft Message Queue Server version 1.0

SYMPTOMS

When Microsoft Message Queue Server (MSMQ) attempts to send a message from a Windows 95 independent client, MSMQ may stop responding (hang) if it is offline.

NOTE: A time out does eventually occur and control is returned to the client application. The application will then work as expected. The time out can vary from 1 to 120 minutes.

CAUSE

This problem occurs because the Windows 95 operating system does not have a Security ID function implemented. To work around this limitation and to verify the credentials on a Windows 95 client, MSMQ makes a remote procedure call (RPC) to its site controller. While it is offline, this RPC stops responding (hangs) until the network subsystem times out. The amount of time that elapses is directly related to the network topology.

WORKAROUND

You can work around this problem in either of two ways.

• You can create a hardware profile that does not have network support and use recoverable messages.

For additional information about setting up the profile, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q183671
TITLE : Optimizing Windows 95 Independent Client for Offline Use

• Use IPX/SPX for network connectivity.

STATUS

Microsoft has confirmed this to be a problem in MSMQ version 1.0. This problem was corrected in Microsoft Windows NT 4.0 Service Pack 4 (SP4).


You can download the fix from Windows NT 4.0 SP4 in the Support\MSMQ.95 directory. The file name is Mq95sp4.exe.

MORE INFORMATION

Please refer to the software development kit (SDK) online documentation for additional information about using the MSMQ ActiveX objects.

Additional query words: mobile remote freeze hang hung respond responding

Keywords          : 
Version           : winnt:1.0
Platform          : winnt 
Issue type        : kbprb 

Last Reviewed: January 26, 1999