Article ID: 330002 - View products that this article applies to.
This article was previously published under Q330002
The Microsoft Message Queuing 2.0 Migration Tool upgrades your Microsoft Message Queue Server 1.0 SQL-based directory service to Microsoft Windows 2000 Active Directory. The migration tool enables the Primary Enterprise Controller (PEC) to upgrade only to the root domain. The upgrade fails on a child domain, and the following errors are displayed:
Error: Unable to delete enterprise object from the MQIS database, hr- c00e0d5fh.
Error: Unable to upgrade the enterprise in MigrateEnterprise(), status - c00e0d5fh.
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 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:
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 -------------------------------------------------------------- 21-Oct-2002 17:31 22.214.171.1249 280,336 Mq1repl.dll 21-Oct-2002 16:38 126.96.36.1999 14,096 Mq1sync.exe 27-Aug-2002 19:54 188.8.131.526 74,832 Mqac.sys 21-Oct-2002 17:31 184.108.40.2067 215,312 Mqads.dll 26-Aug-2002 22:35 220.127.116.116 21,776 Mqbkup.exe 21-Oct-2002 17:31 18.104.22.1680 76,560 Mqdscli.dll 21-Oct-2002 17:31 22.214.171.1245 41,744 Mqdssrv.dll 21-Oct-2002 16:38 126.96.36.1999 98,064 Mqmig.exe 21-Oct-2002 17:31 188.8.131.529 265,488 Mqmigrat.dll 21-Oct-2002 17:31 184.108.40.2060 222,480 Mqoa.dll 21-Oct-2002 17:31 220.127.116.118 8,976 Mqperf.dll 21-Oct-2002 17:31 18.104.22.1688 424,208 Mqqm.dll 21-Oct-2002 17:31 22.214.171.1246 102,672 Mqrt.dll 21-Oct-2002 17:31 126.96.36.1999 70,928 Mqsec.dll 21-Oct-2002 17:31 188.8.131.526 23,824 Mqupgrd.dll 21-Oct-2002 17:31 184.108.40.2066 110,352 Mqutil.dll 21-Oct-2002 17:31 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.