FIX: The Message Queuing replication service does not start automatically when the system starts

Article translations Article translations
Article ID: 834251 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page


The Microsoft Message Queuing (also known as MSMQ) 2.0 replication service may not automatically start when the service is running on Microsoft Windows 2000 Server, and there are no event log entries or other indications that the service has not started. When you try to start the Message Queuing replication service later, the Message Queuing replication service works normally.


This problem may occur when many legacy site controllers exist. During initalization, the replication service makes many calls to the Active Directory service, and these calls may take a long time. Because the service control manager incorrectly interprets this behavior as an unsuccessful attempt to start the Message Queuing replication service, the service control manager shuts down the Message Queuing replication service.


Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 Service Pack 5 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


This hotfix requires that Windows 2000 Service Pack 4 be currently installed before you apply the hotfix.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   02-Jan-2004  17:20         291,088  Mq1repl.dll      
   22-Dec-2003  19:26          14,096  Mq1sync.exe      
   02-Oct-2003  18:21          76,016  Mqac.sys
   02-Jan-2004  17:20         217,360  Mqads.dll        
   20-Sep-2003  16:23          25,360  Mqbkup.exe       
   02-Jan-2004  17:20          76,560  Mqdscli.dll      
   02-Jan-2004  17:20          42,256  Mqdssrv.dll      
   22-Dec-2003  19:26          98,064  Mqmig.exe        
   02-Jan-2004  17:20         266,512  Mqmigrat.dll     
   02-Jan-2004  17:20         222,480  Mqoa.dll         
   02-Jan-2004  17:20          10,000  Mqperf.dll       
   02-Jan-2004  17:20         434,960  Mqqm.dll         
   02-Jan-2004  17:20         102,672  Mqrt.dll         
   02-Jan-2004  17:20          70,928  Mqsec.dll        
   02-Jan-2004  17:20         400,656  Mqsnap.dll       
   02-Jan-2004  17:20          23,824  Mqupgrd.dll      
   02-Jan-2004  17:20         110,864  Mqutil.dll       
   02-Jan-2004  17:20          64,784  Msmq.cpl


Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.


Article ID: 834251 - Last Review: January 17, 2015 - Revision: 2.3
  • Microsoft Message Queuing 2.0
kbnosurvey kbarchive kbfix kbqfe kbhotfixserver KB834251

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from