I have mailboxes migrating from Exchange 2007 to 2013. However, during migration, the DNS server is unavailable and cause the following error. I try to complete the migration after sync but it was completed with error. I try to migrate those mailboxes again, message showed that they were included in the previous batch but it can be completed with success. However, when I check the mailboxes, they are still in Exchange 2007 database. Any idea?

ErrorMessage
"Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNoAccess: Unable to make connection to the server. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    ......
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 2
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 9
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[1]: Long val: 0
    Lid: 44657 
    Lid: 38439   EMSMDBPOOL.EcPoolConnect called [length=48]
    Lid: 42535   EMSMDBPOOL.EcPoolConnect exception [rpc_status=0x5][latency=15]
    Lid: 62184 
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4444
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-18T08:14:49.0320000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 5
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 701
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 2
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 9
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[1]: Long val: 0
    Lid: 44657 
    Lid: 38439   EMSMDBPOOL.EcPoolConnect called [length=48]
    Lid: 42535   EMSMDBPOOL.EcPoolConnect exception [rpc_status=0x5][latency=0]
    Lid: 62184 
    Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 4444
    Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0415-06-18T08:14:49.0320000Z
    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2
    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 5
    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 701
    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 2
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 9
    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[1]: Long val: 0
    Lid: 53361   StoreEc: 0x80070005
    Lid: 51859 
    Lid: 33649   StoreEc: 0x80070005
    Lid: 43315 
    Lid: 58225   StoreEc: 0x80070005
    Lid: 39912   StoreEc: 0x80070005
    Lid: 54129   StoreEc: 0x80070005
    Lid: 50519 
    Lid: 59735   StoreEc: 0x80070005
    Lid: 59199 
    Lid: 27356   StoreEc: 0x80070005
    Lid: 65279 
    Lid: 52465   StoreEc: 0x80070005
    Lid: 60065 
    Lid: 33777   StoreEc: 0x80070005
    Lid: 59805 
    Lid: 52487   StoreEc: 0x80070005
    Lid: 19778 
    Lid: 27970   StoreEc: 0x80070005
    Lid: 17730 
    Lid: 25922   StoreEc: 0x80070005"

You can resume the migration job through the EAC or Powershell.

Check the Exchange 2013 DNS, Default gateway is same as Exchange 2007.

Are you using any backup software for exchange 2007, Such as Symantec Backup Exec, Data protection Manager?

Please disable the services of backup software in Exchange 2007. 

Then try one mailbox at first.

If that works , then try all.

Make sure Exchange 2013 database is good for migrate and it is mounted. Just create a test mailbox in exchange 2013 and assigned to that Database and try to login, in that way we can make sure database is fine.

Make sure your user name has proper permission to do this task, adding your user name under organisation group......

Please look at the below similar thread

https://social.technet.microsoft.com/Forums/exchange/en-US/8aa3c6d6-b284-4a93-8dfe-5c6ca6c090ed/mailbox-move-request?forum=exchange2010

Regards,

Joby

• Edited by Joby M Chacko 18 hours 21 minutes ago
• Proposed as answer by David Wang_Microsoft contingent staff 24 minutes ago

Check the Exchange 2013 DNS, Default gateway is same as Exchange 2007.

Are you using any backup software for exchange 2007, Such as Symantec Backup Exec, Data protection Manager?

Please disable the services of backup software in Exchange 2007. 

Then try one mailbox at first.

If that works , then try all.

Make sure Exchange 2013 database is good for migrate and it is mounted. Just create a test mailbox in exchange 2013 and assigned to that Database and try to login, in that way we can make sure database is fine.

Make sure your user name has proper permission to do this task, adding your user name under organisation group......

Please look at the below similar thread

https://social.technet.microsoft.com/Forums/exchange/en-US/8aa3c6d6-b284-4a93-8dfe-5c6ca6c090ed/mailbox-move-request?forum=exchange2010

Regards,

Joby

• Edited by Joby M Chacko Thursday, June 18, 2015 1:07 PM
• Proposed as answer by David Wang_Microsoft contingent staff Friday, June 19, 2015 7:03 AM

Beside the above given suggestions, I would like to refer you on this well explained technet blog that covers all the required steps while proceeding to migrate from Exchange 2007 to 2013 : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Moreover, when need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on this automated solution (http://www.exchangemigrationtool.com/) that seems to be a good alternative approach in order to accomplish the migration job without having downtime or any further interruption.

Beside the above given suggestions, I would like to refer you on this well explained technet blog that covers all the required steps while proceeding to migrate from Exchange 2007 to 2013 : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Moreover, when need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on this automated solution (http://www.exchangemigrationtool.com/) that seems to be a good alternative approach in order to accomplish the migration job without having downtime or any further interruption.

• Proposed as answer by David Wang_Microsoft contingent staff 6 hours 5 minutes ago

Hi,

I suggest we can use the EAC to create a batch move request.

log in to the EAC and perform the following steps:

In the EAC, navigate to Recipients > Migration, and then click Add Add Icon.

In the New local mailbox move wizard, select the users you want to move, click OK and then click Next.

On the Move configuration page, specify a name for the new batch. Select which options you want for the archive mailbox, and mailbox database location and click New.

For more detailed information, please refer to the link:

https://technet.microsoft.com/en-us/library/jj150487%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Best Regards,

David