Transition from Exchange 2003 to 2010 Mailboxes Will Not Move
I am attempting to transition from Exchange 2003 to Exchange 2010. The Exchange 2003 box is running SP2. The Exchange 2010 box is a Virtural Machine running Hyper-V. The install went fine but when I attempt to move a mailbox either through the Management Console or Management Shell the mail box will stay in the Move Request queue for about 40 minutes than fail. I get the following error message in the Management Console:Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)Diagnostic context: ...... Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0 Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 2348 Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2010-01-12 17:17:17:550 Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 11001 Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 320 Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 1 Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[0]: Unicode string: EXCHANGESERVER.MailServer Lid: 24060 StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115The following error message shows up in the Application LogEvent ID: 1100 Source MSExchange Mailbox ReplicMailbox move for 'domain.com/Users/movetest2' (49074c9a-39af-4f43-b58b-bc9bec9ec5d8) has failed.Error code: -2147221227MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)Diagnostic context: ...... Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0 Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 5648 Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2010-01-21 21:12:25:723 Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18 Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 11001 Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 320 Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 1 Lid: 8856 dwParam: 0x6BA Msg: EEInfo: prm[0]: Unicode string: EXCHANGESERVER.MailServer Lid: 24060 StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115Context:Mailbox: Primary (49074c9a-39af-4f43-b58b-bc9bec9ec5d8)The 2008 box has only NIC and it is not a Small Business Server. We have one 2008 R2 DC in the domain (two 2003 DC's). The firewall is turned off on both boxes.This appears to be either a DNS or permission issue. I have scrubbed DNS and am using an account that has full domain admin rights..Any help will be greatly appreciated.Thank you,Al
January 25th, 2010 8:03pm

I have checked this error and looks like some kind of network error. How ever can you verify if all the servcies are up and running on both the servers. Also can you try to reboot both the boxes and see if that makes a difference.See what Ed (exchange MVP) has to say http://forums.slipstick.com/showthread.php?t=15935Raj
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2010 9:45pm

Hi,Please first check the service on the CAS to make sure the Net.TcpPort Sharing Service is set to Automatic and is running. Also verify that service is running on the Mailbox Server of Exchange 2010.And make sure no firewall is existing between the CAS and Exchange 2003.ThanksAllen
January 27th, 2010 9:54am

Hi Sorry I did not mean to abandon this thread. I thought that I would be notified when someone added a comment. The Net.TcpPort Sharing Service was disabled on the Exchange 2003 box. I changed it to automatic and started the service, but no joy still having the same problem. Since my last comment. The store on the 2003 Exchange box (where all the mail boxes are still located) has dismounted itself twice. And we are unable to create a new mailbox using the 2003 tools. Any additional help will be gratefully appreciated. Thanks you,
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2010 6:29pm

Have you checked the event IDs when the stores went down? Plz post them here.Raj
February 8th, 2010 7:25pm

I ended up opening a case with Microsoft Support to solve this issue. The issue ended up being a network setting in adsiedit.msc.Below is Microsoft's documentation on the trouble shooting steps the took: Problem:-======================Cannot move mailboxes from Exchange 2003 to Exchange 2010 serverTroubleshooting:-======================-You were not able to move mailboxes from Exchange 2003 to Exchange 2010 server,-Move request will stay for about 40 minute and it will fail with an error:-Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)-Database on Exchange 2003 keeps on shutting down, twice in a week.-checked the database on Exchange 2003, it is mounted.-Tried Running the command:-New-MoveRequest -Identity movetest2@domain.com -TargetDatabase "Mailbox Database 1304552153"-we got the same error message after 40 minutes,-Checked the permissions for Administrator account and they were all good,-Ran Exbpa on both the servers, it was clean.-Found SRX081025600255,-There were only 1 NIC on Dc's as well as Exchange servers,-Disabled TCP chimney on Dc's as well as Exchange servers,-For Windows 2003 server :- Netsh int ip set chimney DISABLED-For Windows 2008 server :- netsh int tcp set global chimney=disabled-ran the following command :- IPCONFIG /FLUSHDNS & NET STOP NETLOGON & NET START NETLOGON & NET STOP DNS & NET START DNS & IPCONFIG /REGISTERDNS-Tried moving the mailbox, still the issue was same,-Checked the Application logs on Exchange 2003 server and found event id which says that the Database size on the Exchange 2003 server has reached to 17 GB,-It was Exchange 2003 STD SP2,-we were also getting an error message on log file directory on the properties of Exchange 2003 server,-First we increased the database size limit to 70 GB,http://support.microsoft.com/kb/912375-Then we went to the properties of Exchange 2003 server object in adsiedit.msc-Checked the "Network Address" attribute and it was set to "EXCHANGESERVER.mailserver,-we corrected this value by typing the FQDN of Exchange 2003 server,-we also deleted some "Account unknown" from database objects and gave Exchange 2010 server account full permission on Exchange 2003 database.-restarted the "Exchange Information Store service" on Exchange 2003 server,-Now we do not see an error message for the log file directory on Exchange 2003 server properties in Exchange System Manager,-Tried moving a test mailbox using Exchange power shell,-Mailbox got moved,-we tried another one and it was successfully moved to Exchange 2010 server,-ISSUE RESOVLED.Thanks for all the help offered.Al
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 8:39pm

I had the exact same error. My configuration was that I had two domain in the same forest and Ex2003 was in one domain while we wanted Ex2010 in the new domain. Problem existed because the old server was MAIL.ABC.COM in the ABC Domain and the new server was MAIL.XYZ.COM in the XYZ Domain. When trying to move a mailbox the EX2010 sever only looked for the old mailbox on "MAIL" and since there existed MAIL.XYZ.COM that is what it found but couldn't contact EX2003 on that server. FIX: On the NIC Configurations for the EX2010 servers I put XYZ.COM and first search DNS Zone and then ABC.COM as the second search zone. Now it moves the mailboxes without problems.
May 3rd, 2010 8:08pm

Hi, just as an additional info. I ran into the same problem by migrating from SBS 2003(Exchange 2003) to a 2008 (Exchange 2010) server by one of my clients. After some research I found out that the installed ISA server on the SBS 2003 box was the problem. The RPC filter was blocking the traffic between Exchange 2010 and Exchange 2003. The problem was fixed after disabling the RPC filter. Hope this is helpful for some of you, Roland
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2010 1:44am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics