?
Solved

After migration from Ex2007 to Ex2013 SP1 - mailbox delegation settings: Warning "The object mydomain.com/TestUser1 has been corrupted, and it's in an inconsistent state"

Posted on 2014-04-23
4
Medium Priority
?
5,189 Views
Last Modified: 2014-04-30
Few users were successfully migrated from Exchange 2007 to Exchange 2013 SP1 server. However, migration for some users failed with error message: “Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.”

Trying to resume failed migration batch within exchange admin center is producing the same error.

After some Googling around I have found this article “Corrupted Items and Mailbox Moves in Exchange 2010” (http://windowsitpro.com/exchange-server-2010/corrupted-items-and-mailbox-moves-exchange-2010)

I’m guessing that information in this article is quite relevant to the Exchange 2013 SP1 as well.

Base on the information from the article I’m trying to run following PowerShell command:

Get-MoveRequest -Identity "TestUser1" | Set-MoveRequest -BadItemLimit 20 | Resume-MoveRequest

Output from the command in exchange management shell doesn’t really tells me anything except yellow color warning about possibility of losing some items during the move because of BadItemLimit.

After a while I have noticed that failed status have changed to completed and the mailbox is in correct target database.

Checking properties for the freshly migrated “TestUser1” within Exchange Admin Center looks good so far except for the ‘mailbox delegation’ settings. When I click on it gives me scary warning:

Warning
The object mydomain.com/HR/Admin/TestUser1 has been corrupted, and it's in an inconsistent state. The following validation errors happened:
--------------------------------------------------------------------------------
The access control entry defines the ObjectType 'd819615a-3b9b-4738-b47e-f1bd8ee3aea4' that can't be resolved..
--------------------------------------------------------------------------------
The access control entry defines the ObjectType 'e2d6986b-2c7f-4cda-9851-d5b5f3fb6706' that can't be resolved..
--------------------------------------------------------------------------------
The access control entry defines the ObjectType '9b51a1ef-79b7-4ae5-9ac8-d14c47daca46' that can't be resolved..

What is this?! The word “corrupted” gives me shivers. How do I fix this? If I have too, I can delete this mailbox on Ex2013 and recover it from the backup back to the Ex2007 server but I’m hoping for the easy fix solution if possible.

Thanks in advance
0
Comment
Question by:Olevo
  • 3
4 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 40017282
"Corrupted" means Exchange cannot read it.
In most cases this isn't a problem with the mailbox, but the Active Directory account.
Look at the account in ADUC - I expect on the Security tab there are some accounts which are just the GUID - probably from deleted accounts. Remove them and then wait for replication to occur.

Simon.
1
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40017278
"Corrupted" means Exchange cannot read it.
In most cases this isn't a problem with the mailbox, but the Active Directory account.
Look at the account in ADUC - I expect on the Security tab there are some accounts which are just the GUID - probably from deleted accounts. Remove them and then wait for replication to occur.

Simon.
1
 
LVL 1

Author Comment

by:Olevo
ID: 40027054
Yes, you’re right… I can see few unknown account there. Before I’ll remove them from the security tab I would like to find out who was using those account before.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40031631
If you are seeing the Raw GUID then you will not be able to find out anything because they are now orphaned objects. Removing them is the only thing that you can do.

Simon.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month16 days, 22 hours left to enroll

862 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question