Article ID: 310526 - View products that this article applies to.
This article was previously published under Q310526
This article has been archived. It is offered "as is" and will no longer be updated.
If you try to install Microsoft Message Queuing, also known as MSMQ, 2.0 on a Domain Controller, the installation may fail, and you may receive the following error message:
If Message Queuing 2.0 is already installed, you cannot restart the service, and the following event is logged in the Application Event Log:
0xC00e0013- Unable to establish connection with Active Directory. Verify that there are sufficient permissions to perform this operation.
Event ID: 2063
Unable to successfully complete initialization of the Queue Manager. Message Queuing may function in an unpredictable fashion.
According to Microsoft Knowledge Base article 191989
(http://support.microsoft.com/kb/191989/EN-US/ ), error 0xC00e0013 is a generic error. This error can occur if several configuration settings are not set correctly. Verify that the permissions on the following items are set correctly:
Hotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, 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:
PrerequisitesNo prerequisites are required.
File informationThe 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 -------------------------------------------------------------- 28-Aug-2003 17:54 22.214.171.1248 281,360 Mq1repl.dll 17-Jun-2003 14:33 126.96.36.1998 14,096 Mq1sync.exe 28-Aug-2003 15:00 188.8.131.523 76,144 Mqac.sys 28-Aug-2003 17:54 184.108.40.2063 217,360 Mqads.dll 30-Oct-2002 13:43 220.127.116.111 25,360 Mqbkup.exe 28-Aug-2003 17:54 18.104.22.1688 76,560 Mqdscli.dll 28-Aug-2003 17:54 22.214.171.1243 42,256 Mqdssrv.dll 21-Oct-2002 17:31 126.96.36.1999 98,064 Mqmig.exe 28-Aug-2003 17:54 188.8.131.529 265,488 Mqmigrat.dll 28-Aug-2003 17:54 184.108.40.2060 222,480 Mqoa.dll 28-Aug-2003 17:54 220.127.116.113 9,488 Mqperf.dll 28-Aug-2003 17:54 18.104.22.1683 431,888 Mqqm.dll 28-Aug-2003 17:54 22.214.171.1248 102,672 Mqrt.dll 28-Aug-2003 17:54 126.96.36.1996 70,928 Mqsec.dll 28-Aug-2003 17:54 188.8.131.523 400,656 Mqsnap.dll 28-Aug-2003 17:54 184.108.40.2062 23,824 Mqupgrd.dll 28-Aug-2003 17:54 220.127.116.112 110,864 Mqutil.dll 28-Aug-2003 17:54 18.104.22.1688 64,784 Msmq.cpl 28-Aug-2003 19:55 22.214.171.124 639,848 Windows2000-kb310526-x86-enu-symbols.exe 28-Aug-2003 19:57 126.96.36.199 1,005,928 Windows2000-kb310526-x86-enu.exe
To work around this problem, follow these steps on the Domain Controller:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To reproduce this behavior, add conflicting subnet information inside DNS.
If error logging is enabled, you may see symptoms that are similar to the following in the Message Queuing 2.0 error log:
0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/230. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/180. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/170. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/30. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/10. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/ipsite/20. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqdscore/dscore/140. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: MQADS Error: mqads/mqdsapi/500. HR: c00e0001 0xc04> Mon Apr 19 12:28:38 2004: DSSRV Error: mqdssrv/dsapi/360. HR: c00e0001
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New naming schema for Microsoft Windows hotfix packages
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/191989/ )Error Message: Error 0xc00e0013, No connection with the site controller
Contact us for more help
Connect with Answer Desk for expert help.