The bind syntax is not correctly interpreted
This article was previously published under Q329546
This article has been archived. It is offered "as is" and will no longer be updated.
When Microsoft Message Queuing, also known as MSMQ, 2.0 is recycled, the following invalid DNS query is generated:
_ldap._tcp.my-site._sites.dc._msdcs.serverThis invalid DNS query occurs because the following call is made:
ADsOpenObject("LDAP://server/DC=domain, DC=com",...)Instead, the following call should be made:
ADsOpenObject("LDAP://domain.com/DC=domain, DC=com", ...)
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA 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 4 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix 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 ------------------------------------------------------ 24-Oct-2002 19:55 18.104.22.1689 280,336 Mq1repl.dll 21-Oct-2002 15:38 22.214.171.1249 14,096 Mq1sync.exe 27-Aug-2002 18:54 126.96.36.1996 74,832 Mqac.sys 24-Oct-2002 19:55 188.8.131.520 217,360 Mqads.dll 26-Aug-2002 21:35 184.108.40.2066 21,776 Mqbkup.exe 24-Oct-2002 19:55 220.127.116.110 76,560 Mqdscli.dll 24-Oct-2002 19:55 18.104.22.1685 41,744 Mqdssrv.dll 21-Oct-2002 15:38 22.214.171.1249 98,064 Mqmig.exe 24-Oct-2002 19:55 126.96.36.1999 265,488 Mqmigrat.dll 24-Oct-2002 19:55 188.8.131.520 222,480 Mqoa.dll 24-Oct-2002 19:55 184.108.40.2068 8,976 Mqperf.dll 24-Oct-2002 19:55 220.127.116.118 424,208 Mqqm.dll 24-Oct-2002 19:55 18.104.22.1686 102,672 Mqrt.dll 24-Oct-2002 19:55 22.214.171.1249 70,928 Mqsec.dll 24-Oct-2002 19:55 126.96.36.1996 23,824 Mqupgrd.dll 24-Oct-2002 19:55 188.8.131.526 110,352 Mqutil.dll 24-Oct-2002 19:55 184.108.40.2068 64,784 Msmq.cpl
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
Article ID: 329546 - Last Review: 02/27/2014 21:15:18 - Revision: 2.4
Microsoft Message Queuing 2.0
- kbnosurvey kbarchive kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix KB329546