Message Queuing workgroup server quits when used as a supporting server by a dependent client (311567)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q311567

SYMPTOMS

When a dependent client attempts to use the Microsoft Message Queuing workgroup server as its supporting server, the server quits or stops responding (crashes).

CAUSE

When a Message Queuing-dependent client first connects to its supporting server, the client queries the server for the Message Queuing Enterprise globally unique identifier (GUID). Because this is the Message Queuing workgroup mode, the topology structure is never initialized, and therefore the server quits.

RESOLUTION

This fix is implemented on the server. With this fix, the server will now determine whether it is in workgroup mode and respond to the query from the client with a null GUID. A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English-language version of this fix should have the following file attributes or later:
   Date           Time  Version    Size       File name     
   -------------------------------------------------------
   02/28/2001   17:54  5.0.0.720    273kb  mq1repl.dll
   02/28/2001   17:47  5.0.0.720     14kb  mq1sync.dll
   02/28/2001   17:47  5.0.0.733     70kb  mqac.sys
   02/28/2001   17:54  5.0.0.721    210kb  mqads.dll
   02/28/2001   17:47  5.0.0.720     22kb  mqbkup.exe
   02/28/2001   17:54  5.0.0.720     29kb  mqcertui.dll
   02/28/2001   17:54  5.0.0.720     49kb  mqclus.dll
   02/28/2001   17:54  5.0.0.720     30kb  mqdbodbc.dll
   02/28/2001   17:54  5.0.0.720     74kb  mqdscli.dll
   02/28/2001   17:54  5.0.0.720     41kb  mqdssrv.dll
   02/28/2001   17:47  5.0.0.720     96kb  mqmig.exe
   02/28/2001   17:54  5.0.0.720    258kb  mqmigrat.dll
   02/28/2001   17:54  5.0.0.720    219kb  mqoa.dll
   02/28/2001   17:54  5.0.0.720      8kb  mqperf.dll
   02/28/2001   17:54  5.0.0.733    406kb  mqqm.dll
   02/28/2001   17:54  5.0.0.720      9kb  mqrperf.dll
   02/28/2001   17:54  5.0.0.733     90kb  mqrt.dll
   02/28/2001   17:54  5.0.0.720     69kb  mqsec.dll
   02/28/2001   17:54  5.0.0.720    391kb  mqsnap.dll
   02/28/2001   17:48  5.0.0.720     14kb  mqsvc.exe
   02/28/2001   17:54  5.0.0.720     24kb  mqupgrd.dll
   02/28/2001   17:54  5.0.0.720    106kb  mqutil.dll
   02/28/2001   17:54  5.0.0.720     64kb  msmq.cpl
   02/28/2001   17:54  5.0.0.720    156kb  msmqocm.dll
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:10/6/2005
Keywords:kbprb kbQFE KB311567