Share via

new-moverequest / new-migrationbatch is failing if msExchExtensionAttribute45 is set

  • Article
  • 07/19/2016

Question

Tuesday, July 19, 2016 7:11 PM

Hello everyone

today we noticed that all moverequests / migration batches  are failing if the msExchExtensionAttribute45 is not empty.

Is this a known limitation or just a bug ?

We are trying to migrate exchange 2010 mailboxes to ex2016 ...

You will get an absolute helpless error message if you running into this error.

Could not convert property AuditStorageState to type AuditStorageState. Error while converting string
'xxxxxx.com' to result type Microsoft.Exchange.Data.Directory.Recipient.AuditStorageState: Conversion failed due
to invalid enumeration value. Please specify one of the following enumeration values and try again. The possible
enumeration values are "None, Online, Offline".
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], DataValidationException
    + FullyQualifiedErrorId : [Server=server,RequestId=3d035a42-0628-41bc-9767-c5b8e6dc8526,TimeStamp=7/20/2016 6:58
   :39 AM] [FailureCategory=Cmdlet-DataValidationException] 929A982F,Microsoft.Exchange.Management.Migration.MailboxR
  eplication.MoveRequest.NewMoveRequest
    + PSComputerName        : server.domain.net

Try to Google this one this is just a dead end ...

The error you will get if you try to start a new-migrationbatch is completely different , this error is something that the destination user cannot be found ...

If we clean the attribute45 the moverequest will be executed without a problem.

Can someone confirm that this error is just a BUG or an known limitation?

Maybe someone will also run into this error and this thread could help to solve the problem.

Thx

Christoph

All replies (4)

Wednesday, July 20, 2016 5:58 AM ✅Answered | 3 votes

Hi Christoph,

According to your description, I notice that failed to move mailbox from Exchange 2010 to Exchange 2016 if msExchExtensionAttribute45 is not empty, however it works correct if it's empty.

I reproduce your issue if there's something in msExchExtensionAttribute45, however the possible values of this attribute is "None, Online, Offline", you can change it to one of them and it will works correctly.

Moreover, this attribute added after Exchange 2010 SP2 and it's not exposed to various CMDlets and Exchange management UI (it'll not return if run Get-Mailbox xxxx| FL *attribute* in Exchange 2016, and display account corrupted if it's invalid.). More details about it, please refer to: https://blogs.technet.microsoft.com/exchange/2012/01/17/custom-aka-extension-attributes-in-exchange-2010-sp2-and-their-use/

For now, we recommend don't use this attribute, please clear this value in msExchExtensionAttribute45, then add it to "ExtensionAttrinute1 to 15" for your convenience.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

Allen Wang
TechNet Community Support

Wednesday, July 20, 2016 4:54 AM | 1 vote

Please refer to this guide which include series of article for exchange 2010 to 2016 migration and ensure you are following all the required steps: http://www.msexchange.org/articles-tutorials/exchange-2016-articles/migration-deployment/migrating-small-organization-exchange-2010-exchange-2016-part1.html

As a workaround, also check this: http://technet.microsoft.com/en-us/library/dd876880.aspx

Manage migration batches in Exchange Online

You may also get help from this blog to move mailboxes from Exchange 2010 to Exchange 2016 using Exchange Admin Center: http://mstechtalk.com/migrating-to-exchange-2016-using-the-exchange-admin-center/

Hope this helps!

Migrate mailboxes, Public Folders, Outlook profiles and rules and GAL etc. to-and-fro Exchange Servers and Office 365 with LepideMigrator for Exchange

Wednesday, July 20, 2016 7:01 AM

Hey Allen,

thx for clarifying this and providing me the background information.

So its an known "limitation"

I will remove my information from that attribute and use some of the supported ones.

Have a nice day

Christoph 

Wednesday, July 20, 2016 9:05 AM

Hi,

Thank you for your reporting back.

Actually, this issue occurs if we set wrong value for msExchExtensionAttribute45.

Anyway, if it works and help, please mark it as answers. Thank you for your cooperation.

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

Allen Wang
TechNet Community Support