none
Exchange 2003 - 2010 Mailbox Migration Error

    Question

  • I have a single frontend/backend exchange 2003 server that i am attempting to migrate a mailbox to a 2 server exchange 2010.  Same domain migration. The Mailbox GUID listed below is the exchange 2003, and is actually online.  Any ideas on what could cause this error?

    (PID 3440, Thread 149) Task New-MoveRequest writing error when processing record of index 0. Error: Microsoft.Exchange.MailboxReplicationService.MailboxReplicationTransientException: Service 'net.tcp://nv-excas1/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: Mailbox database 'a0dd10be-fa72-47bd-afb4-0bf3ce7175e' is offline. ---> Microsoft.Exchange.MailboxReplicationService.MailboxReplicationTransientException: Exception details: MailboxReplicationTransientException (80040111): Mailbox database 'a0dd10be-fa72-47bd-afb4-0bf3ce7175e' is offline. ---> Microsoft.Exchange.MailboxReplicationService.MailboxReplicationTransientException: Exception details: MapiExceptionLogonFailed (80040111): MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
    Diagnostic context:
        ......
        Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string: NV-EXCHANGE
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -545057711
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
        Lid: 45169   StoreEc: 0x824    
        Lid: 44273 
        Lid: 37053   Win32Error: 0x6A6
        Lid: 23065   EcDoConnectEx called [length=112]
        Lid: 17913   EcDoConnectEx returned [ec=0x3F2][length=56][latency=15]
        Lid: 56945 
        Lid: 23065   EcDoConnectEx called [length=112]
        Lid: 17913   EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
        Lid: 59505   StoreEc: 0x3F2    
        Lid: 52465   StoreEc: 0x3F2    
        Lid: 60065 
        Lid: 33777   StoreEc: 0x3F2    
        Lid: 59805 
        Lid: 52209   StoreEc: 0x3F2    
        Lid: 19778 
        Lid: 27970   StoreEc: 0x3F2    
        Lid: 17730 
        Lid: 25922   StoreEc: 0x3F2    
       --- End of inner exception stack trace ---
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallService(GenericCallDelegate del, String epAddress)
       at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.GetMailboxInformation(Guid primaryMailboxGuid, Guid physicalMailboxGuid, Guid targetMdbGuid, String targetMdbName, String remoteHostName, String remoteOrgName, String remoteDCName, NetworkCredential cred)
       at Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    Sys Admin - MCSE
    • Edited by Kevin_Manson Wednesday, November 18, 2009 5:57 PM update title
    Tuesday, November 17, 2009 12:38 PM

Answers

  • Hey guys, i was working on an Exchange 2003 to 2010 migration and came up with the same error... I went to Exchange System Management on the Exchange 2003 Server and right clicked on the First Storage Group\Mailbox Store; Security Tab; then added a Computer Object(EXG01) and gave it Full Control... I was then able to use Exchange Server 2010 to utilize the "New Local Move Request" to the Exchange 2010 Database... Please reply and let me know if this helped you!

    You might also find some of my blogs interesting!

    -NS
    Thursday, December 3, 2009 9:42 PM

All replies

  • I have a single frontend/backend exchange 2003 server that i am attempting to migrate a mailbox to a 2 server exchange 2010.  Same domain migration. The Mailbox GUID listed below is the exchange 2003, and is actually online.  Any ideas on what could cause this error?

    ...

    (80040111): MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)

    ...

    Sys Admin - MCSE

    Hi Kevin,

    Stupid questions, I know, but your CAS and Mailbox roles are up and running? Can you setup a new mailbox and connect to it?

    Yannick
    Tuesday, November 17, 2009 1:50 PM
  • Yannick,

    Yes, I have created a test mailbox on the 2010 server, and successfully connected via OWA.
    Sys Admin - MCSE
    Tuesday, November 17, 2009 3:01 PM
  • Kevin,

    Some of these questions might be stupid, but we all overlook some of these items:

    You are executing the mailbox moves from the Exchange 2010 mailbox server?  Exchange 2003 is running SP2 and is online?  Can you ping the Exchange 2003 server from the Exchange 2010 mailbox server?   Can you use MFCMapi to open a mailbox on Exchange 2003 from the Exchange 2010 mailbox server?

    The account you are using to move mailboxes has Exchange Administrative permissions in the source Administrative Group on Exchange 2003?  The same account is either in the Recipient Management or Organization Management groups in Exchange 2010?

    If you are still having problems, increase the logging on both Exchange 2003 MSExchangeIS as per: http://support.microsoft.com/kb/821829 and Exchange 2010 with the following command:

    Get-EventLogLevel -Identity MsExchangeIS\* | Set-EventLogLevel -Level Expert

    Check the event viewer on both servers for more information which may hopefully assist in troubleshooting.

    To return the logging to normal, execute the following command:

    Get-EventLogLevel -Identity MsExchangeIS\* | Set-EventLogLevel -Level Lowest
    Sean | http://seanv.wordpress.com
    Tuesday, November 17, 2009 3:41 PM

  • Sean,

    I have attempted the move from both the MBX and CAS servers, Exchange2003 SP2 is online. Yes i can ping the 2003 server.  I can connect with MFCMapi to the account i am trying to move.

    I am moving the Administrator users mailbox with the administrator user.

    Increasing logging on the 2010 side had no extra information, Logging MSExchangeIS Connections for 2003 gave me the error below.

    Event Type:    Error
    Event Source:    MSExchangeIS
    Event Category:    Connections
    Event ID:    1021
    Date:        11/17/2009
    Time:        2:21:30 PM
    User:        N/A
    Computer:    NV-EXCHANGE
    Description:
    DOMAIN/NV-EXCAS1$ was unable to connect as /o=DOMAIN/ou=First Administrative Group/cn=Recipients/cn=Administrator. Error 0x3f2.

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Sys Admin - MCSE
    Tuesday, November 17, 2009 7:27 PM
  • No problem to move a mailbox in Exchange 2003 (just to be sure that the system attendant mailbox is OK)?

    Yannick
    Wednesday, November 18, 2009 12:47 PM
  • Try to add your Exchange 2003 Server to: Exchange Domain Servers group, Exchange Servers group.
    Wednesday, November 18, 2009 1:50 PM
  • Yannick,

    I have a strange workaround to the problem.   Take a mailbox new or old, and move it as described below
    • Exchange 2003 First storage group --> Exchange 2010 (Failure)
    • Exchange 2003 First storage group --> Exchange 2003 Second storage group  --> Exchange 2010 (Success)
    • Exchange 2003 First storage group --> Exchange 2003 Second storage group  --> Exchange 2003 First storage group -->  Exchange 2010 (Success)
    Any Thoughts?
    Sys Admin - MCSE
    Wednesday, November 18, 2009 5:56 PM
  • That is a very odd problem, but I am glad that you have a work around.  I did notice that I told you to increase the logging for the MSExchangeIS service.  You can also try to increase the logging for the MRS Service which is what is actually performing the mailbox move.

    To increase:
    Get-EventLogLevel -Identity "MSExchange Mailbox*" | Set-EventLogLevel -Level Expert

    To reset:
    Get-EventLogLevel -Identity "MSExchange Mailbox*" | Set-EventLogLevel -Level Lowest

    However, based on the information you have provided thus far, I doubt that this will reveal any additional information to solve your problem.  I do think that that if you are migrating from the Exchange 2003 server that you should follow your work around.  If you do need to (or want to) solve the issue, then I believe you might need to open a ticket with Microsoft PSS for more indepth investigation.
    Sean | http://seanv.wordpress.com
    Friday, November 20, 2009 5:34 AM
  • Did something silly like the system mailbox from that 1st storage group get deleted? Have you tried dismounting/mounting the DB(s) in the first storage group and reattempting the move?
    Brian Day, Overall Exchange & AD Geek
    MCSA 2000/2003, CCNA
    MCTS: Microsoft Exchange Server 2010 Configuration
    LMNOP
    Friday, November 20, 2009 5:40 AM
  • I have the same problem here.

    I just tried the workaround: (In my case, the third option has not worked. It really seem that I have a problem with the security of my first storage group)

  • Exchange 2003 First storage group --> Exchange 2010 (Failure)
  • Exchange 2003 First storage group --> Exchange 2003 Second storage group  --> Exchange 2010 (Success)
  • Exchange 2003 First storage group --> Exchange 2003 Second storage group  --> Exchange 2003 First storage group -->  Exchange 2010 (Failure)
  • I tried to dismounting/mounting the DB(s) in the first storage group and reattempting the move but it's not better.

Monday, November 23, 2009 3:06 AM
  • Hello Kevin,

    i had recently faced a similar issue and it was due to the permission inheritance bloced on the First Storage group. We also had incorrect Schema update for Exchange 2010. You can try running the Exchange Best Practices Analyser for identifying permission issue if any.

    Hope this helps...!
    Wednesday, November 25, 2009 3:57 PM
  • Hey guys, i was working on an Exchange 2003 to 2010 migration and came up with the same error... I went to Exchange System Management on the Exchange 2003 Server and right clicked on the First Storage Group\Mailbox Store; Security Tab; then added a Computer Object(EXG01) and gave it Full Control... I was then able to use Exchange Server 2010 to utilize the "New Local Move Request" to the Exchange 2010 Database... Please reply and let me know if this helped you!

    You might also find some of my blogs interesting!

    -NS
    Thursday, December 3, 2009 9:42 PM
  • Dear n8dog89,
    Yes your solution solved my problem, thanks.
    Saturday, December 5, 2009 9:59 PM
  • I have the same issue, except I am doing an Ex2003 to Ex2010 migration cross-forest. I have tried to give the Ex2010 CAS server doing the move full control as you suggest, but this did not resolve my problem.
    Friday, December 11, 2009 4:01 PM
  • Have you created a trust between the forests? Have you read this thread ? Also this Google Search might help you out.

    Regards,
    NS
    The IT Guy
    EPIC Information Solutions
    Winnipeg, MB
    Friday, December 11, 2009 5:27 PM
  • Yes, I have a 2-way external trust between the 2 forests. My source forest contains E2K3 Sp2 in Mixed-Mode. My target forest contains a single 2007 Mbx/HT/CAS server, and multiple 2010 HT/CAS/Mbx servers. I am able to migrate the user successfully between source 2003 and destination 2007 using "move-mailbox" cmdlet. However, if I try using new-moverequest on a 2010 CAS, i get the "Unable to make connection to server" MAPIExceptionNetwork error. I'm using the same credentials with both commands.
    Friday, December 11, 2009 6:53 PM
  • My issue was I could not resolve hosts in the source domain via shortname.  The trust was setup, and DNS was working in that I could ping the fqdn of severs in the source domain, but short name was not resolving.  After I setup DNS search suffixes in my TCP/IP settings for the trust domains, and could ping by short name, the new-moverequest cmdlet was succesfull.  Interestingly though, short name resolution was also not working on my 2007 Exhange CAS, but move-mailbox worked fine.

    Now I just have to find out why after I succesfully move the mailbox, it is not useable because "get-calendarprocessing cannot open mailbox".  I can "set-calendarprocessing -identity 'user' -automateprocessing autoupdate" and this fixes it.  But why must I do this on all mailboxes that are migrated?

    Wednesday, December 16, 2009 11:21 PM
  • Hi,
     
    Please check the following blog to know about Cross Forest Move Mailbox Request from Exchange 2003 to 2010 Step-by-Step with Screenshots.

    Ref to:
    Cross Forest Move Mailbox Request from Exchange 2003 to 2010

    All the Best :)


    Sathish Kumar Elango | MCSE 2003 & MCSA Messaging | http://msexchangehelp.wordpress.com
    Saturday, March 13, 2010 5:19 AM
  •  your solution solved my problem, thanks
    • Edited by Duran_ap Wednesday, May 26, 2010 3:56 PM
    Tuesday, May 18, 2010 11:21 PM
  •  i was working on an Exchange 2003 to 2010 migration and came up with the same error ... I went to Exchange System Management on the Exchange 2003 Server and right clicked on the First Storage Group\Mailbox  Store; Security Tab; then added a Computer Object(EXG01) and gave it Full Control... I was then able to use Exchange Server 2010 to utilize the "New Local Move Request" to the Exchange 2010 Database ... 

    this is a dupe of my post above, someone please delete it... ie the post by Duran_ap
    Sunday, May 23, 2010 11:02 PM
  • That worked for me too!  You're a life saver!

    -ES


    Evan Soenke
    Monday, June 14, 2010 8:05 AM
  • Thanks.  I had the exact same problem and this fixed it for me.
    Friday, July 23, 2010 6:38 PM
  • I'm having the exact same problem and would love to try this trick, but unfortunately, my Exchange 2003 is Standard Edition, so I cannot create a second storage group.  Does anybody have any suggestions?  In my case, I can't move any of my 2003 resource mailboxes.  Same error.  Nothing revealed with diagnostic logging.
    Friday, August 13, 2010 9:20 PM
  • Read up the list for N8dog89s solution, he hit the nail on the head, done 3 of these upgrades and permissions, permissions, even when the error was saying the Database was Offline.

    Best of luck.


    Thursday, October 21, 2010 3:50 PM
  • it did solve my problem. Thanks for sharing
    Wednesday, November 3, 2010 9:03 PM
  • N8dog89,

    Thanks for your solution, helped me out migrating mailboxes from SBS2003 to Exch2010. Cheers!

    Jay


    Jay Valambhia |  www.netflo.co.uk



    • Edited by Jay Vee Friday, January 20, 2012 5:59 PM
    Saturday, May 28, 2011 11:22 AM
  • Hey guys, i was working on an Exchange 2003 to 2010 migration and came up with the same error... I went to Exchange System Management on the Exchange 2003 Server and right clicked on the First Storage Group\Mailbox Store; Security Tab; then added a Computer Object(EXG01) and gave it Full Control... I was then able to use Exchange Server 2010 to utilize the "New Local Move Request" to the Exchange 2010 Database... Please reply and let me know if this helped you!

    You might also find some of my blogs interesting!

    -NS
    That solution worked for me!  Thank you!!!

    Give a man fire, you keep him warm for a day. Set a man on fire and you'll keep him warm for the rest of his life.
    Tuesday, October 18, 2011 9:46 PM
  • Worked for me too.
    Thursday, January 19, 2012 11:29 PM
  • thank you, thank you, thank you.

    Wednesday, August 15, 2012 12:48 AM
  • In my case it was Trend Micro Blocking the Move task.  Unloaded it, and it worked.  SO make sure you do not have antivirus/firewall software blocking it
    Saturday, February 16, 2013 2:41 PM
  • for me

    cause mailbox masqued for address book


    vsd

    Monday, July 29, 2013 10:32 AM
  • Detailed instructions here.

    http://supertekboy.com/2013/12/10/1101/


    -digsaw

    Tuesday, January 7, 2014 1:58 AM
  • Or delete the mailbox and reconnect it as a workaround if it's only one that is acting up.
    Monday, November 17, 2014 4:28 AM