hi,

this blog has the answer for your error.

http://social.technet.microsoft.com/wiki/contents/articles/15842.mailbox-migration-fails-with-error-cannot-open-system-attendant-mailbox-in-exchange-server-2013.aspx

get-mailbox -arbitration

Regards

Viman

• Marked as answer by Daniel-Dawson Sunday, April 21, 2013 6:50 AM

Hello,

Hoping someone could help with this error im getting. When i do a mailbox move from 2010 to 2013 using the 2013 Gui. I get an error saying ......

Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE/cn=Microsoft System Attendant.

Environment details are: 

DC 2008r2

Exchange 2010 on 2008 r2

Exchange 2013 on 2008 r2

Has any come across this before?

Thanks

hi,

this blog has the answer for your error.

http://social.technet.microsoft.com/wiki/contents/articles/15842.mailbox-migration-fails-with-error-cannot-open-system-attendant-mailbox-in-exchange-server-2013.aspx

get-mailbox -arbitration

Regards

Viman

Hi,

Apologies if this seems really obvious but did you upgrade to CU1 and is Exchange 2010 at SP3?

What happens if you try to move the mailbox via the  Exchange 2010 GUI?

H

• Edited by Hardeep Bains Thursday, April 11, 2013 1:23 PM

Hi Viman

Thank you for the reply,

I checked out the article but still no luck, Both my databases are mounted.

Any other ideas?

Thanks for your help.

Hi,

Apologies if this seems really obvious but did you upgrade to CU1 and is Exchange 2010 at SP3?

What happens if you try to move the mailbox via the  Exchange 2010 GUI?

H

Did you delete the default mailbox database which got created automatically during the installation?

• Proposed as answer by Simon_WuMicrosoft contingent staff, Moderator Monday, April 15, 2013 8:42 AM

Did you delete the default mailbox database which got created automatically during the installation?

We're running into the same issue, moving from Exchange 2007 to 2013. All of the most recent patches and rollups are installed on all servers. All databases are showing as mounted, and all necessary mailboxes return in the get-mailbox -arbitration request.

DC 2008r2/2012

Exchange 2007 (version 8.3, build 83.6) on 2008r2 (1 CA, 1 HT, 3 MB servers)

Exchange 2013 (version 15.0, build 516.32) on 2012 (1 CAS, 2 MB servers)

DAG with 2 servers, 2 databases

Appreciate any feedback!

Royal

We're running into the same issue, moving from Exchange 2007 to 2013. All of the most recent patches and rollups are installed on all servers. All databases are showing as mounted, and all necessary mailboxes return in the get-mailbox -arbitration request.

DC 2008r2/2012

Exchange 2007 (version 8.3, build 83.6) on 2008r2 (1 CA, 1 HT, 3 MB servers)

Exchange 2013 (version 15.0, build 516.32) on 2012 (1 CAS, 2 MB servers)

DAG with 2 servers, 2 databases

Appreciate any feedback!

Royal

I am in the same situation as this with Exchange 2007 and Exchange 2013 all as up to date as I can get them and I get the same error with the system attendant when I try to migrate a mailbox.

I hate to tag onto this thread, but I was wondering if this ever got solved.   We are in the process of migrating from Exchange 2007 to 2013 and can not get the room resources to move, based on the same error that has been posted here.   All servers are updated and patched.  I am going to open a support case tomorrow, and will post comments after that if anyone likes unless someone responds with a fix.

thanks,

I hate to tag onto this thread, but I was wondering if this ever got solved.   We are in the process of migrating from Exchange 2007 to 2013 and can not get the room resources to move, based on the same error that has been posted here.   All servers are updated and patched.  I am going to open a support case tomorrow, and will post comments after that if anyone likes unless someone responds with a fix.

thanks,

I am in the exact same situation as you, 2007 to 2013 and resource mailboxes in the test environment have the "Cannot open mailbox ... System Attendant". Was Microsoft able to help out?

Same situation here... Hoping someone will respond...

Hello,

Each Exchange server has one System Attendant mailbox. System Attendant mailbox is also required to be available during mailbox moves.

If this messed around with the servers you will come across with this error message. If you notice any events 9175, 9167, and 1008 in your application event log during mailbox move failure.

Refer the below article to fix it.

http://support.microsoft.com/kb/264413/en-us

http://exctech2013.blogspot.com/2013/05/part7-exchange-2010-to-2013-migration.html

Hello,

Each Exchange server has one System Attendant mailbox. System Attendant mailbox is also required to be available during mailbox moves.

If this messed around with the servers you will come across with this error message. If you notice any events 9175, 9167, and 1008 in your application event log during mailbox move failure.

Refer the below article to fix it.

http://support.microsoft.com/kb/264413/en-us

http://exctech2013.blogspot.com/2013/05/part7-exchange-2010-to-2013-migration.html

This is still just saying to mount the database.  For me, and evidently many others, the databases are mounted and the mailboxes are online.  Despite this fact, we are still receiving the error.  

Another person tagging onto the thread.  You stated that you were going to open a support case; did you and what was the resolution?

I am able to move standard user mailboxes using the GUI, but in this instance, I am trying to move Resource mailboxes.

I was able to move the Resource (Conference Room) using this cmdlet, but I don't like to use cmdlets.

New-MoveRequest -Identity "MailboxAlias" -TargetDatabase "DataBase"

Thanks,

Willis

• Edited by wilmiester 13 hours 5 minutes ago Add content