The value of property 'RecipientTypeDetails', 536870912, is not defined in the Enum type 'RecipientTypeDetails'.

When you run the command Get-Mailbox, it throws the warning on DiscoverySearchMailbox.


WARNING: Object exchangeranger.in/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted and it is in an inconsistent state. The followng validation error has occurred:WARNING: The value of property ‘RecipientTypeDetails’, 536870912, is not defined in the Enum type ‘RecipientTypeDetails’.


Check the Adsiedit.msc —>Domain Context (Domain Partition)—>Users—>DiscoverySearchMailbox, go to the properties and locate the attribute msExchRecipientTypeDetails.

As we know, DiscoverySearchMailbox is User Mailbox, hence for Object Type for User Mailbox, the decimal value should be 1. In this issue the decimal value is 536870912.

I checked the same attribute on my mailbox and found that, the decimal value is set to 1, which is correct.

Change the decimal value 536870912 to 1 on DiscoverySearchMailbox by going at the location Adsiedit.msc —>Domain Context (Domain Partition)—>Users—>DiscoverySearchMailbox, go to the properties and locate the attribute msExchRecipientTypeDetails

Once you set the decimal value to 1, run the command Get-Mailbox and you should get the below result.

Here is the list of Object Type with there decimal values in exchange server.


Note:
If you don’t fix this warning and ignore it, DiscoverySearchMailbox feature won’t work.

Cheers,

About the Author

Gulab Prasad

Technology Consultant & Blogger

MCSE: Exchange Server 2016, 2013
MCSE: Skype for Business Server 2015
MCSE: Azure Productivity
MCSE: Windows Server 2016
MCSA: Windows Server 2012, Office 365
MCITP: Exchange Server 2010-2007 | Lync Server 2010
VMware: vSphere 6 Foundations

4 Comments

  1. I don't think we are supposed to modify anything. This has happened because you have viewed with EMC of a lower version compared to the higher one being migrated to. Discovery Search Mailboxes don't exist in Exchange 2007.

  2. No, I was getting same error when I viewed in Exchange 2010 EMS. I have seen this issue few times in Exchange 2007 and 2010 Coexistence environment.

Leave a Reply

Your email address will not be published. Required fields are marked *