Article ID: 328141 - View products that this article applies to.
This article was previously published under Q328141
When you run the Microsoft Message Queuing migration tool a second time, the tool may delete the MsmqServices object by mistake.
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:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA 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 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:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMSNOTE: 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 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 -------------------------------------------------------------- 27-Aug-2002 22:55 22.214.171.1246 280,336 Mq1repl.dll 27-Aug-2002 22:54 126.96.36.1996 14,096 Mq1sync.exe 27-Aug-2002 22:54 188.8.131.526 74,832 Mqac.sys 27-Aug-2002 22:55 184.108.40.2066 215,312 Mqads.dll 27-Aug-2002 01:35 220.127.116.116 21,776 Mqbkup.exe 27-Aug-2002 22:55 18.104.22.1680 76,560 Mqdscli.dll 27-Aug-2002 22:55 22.214.171.1245 41,744 Mqdssrv.dll 27-Aug-2002 22:54 126.96.36.1996 98,064 Mqmig.exe 27-Aug-2002 22:55 188.8.131.526 264,976 Mqmigrat.dll 27-Aug-2002 22:55 184.108.40.2060 222,480 Mqoa.dll 27-Aug-2002 22:55 220.127.116.118 8,976 Mqperf.dll 27-Aug-2002 22:55 18.104.22.1686 423,696 Mqqm.dll 27-Aug-2002 22:55 22.214.171.1246 102,672 Mqrt.dll 27-Aug-2002 22:55 126.96.36.1996 70,416 Mqsec.dll 27-Aug-2002 22:55 188.8.131.526 23,824 Mqupgrd.dll 27-Aug-2002 22:55 184.108.40.2066 110,352 Mqutil.dll 12-Jul-2002 16:54 220.127.116.118 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.