none
Exchnage Mailbox corrupted warning RRS feed

  • Question

  • Hi guys 

    I am in the middle of a migration from exchange 2007 (on SBS) to exchange 2013 (on windows server 2012)

    1- I installed exchange 2013 and everything is working ok

    2-started migrating test users from exchange 2007 to 2013 and its working just fine

    issues:

    am having an exchange warning on MEC (SBS) ==> "The value of property 'RecipientTypeDetails', 536870912, is not defined in the Enum type 'RecipientTypeDetails'."

    even if I run the get-mailbox command from EMS (SBS) I get the same warning in yellow ==>

    WARNING: Object ma.local/MyBusiness/Users/SBSUsers/DiscoverySearchMailbox
    {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted and it is in an
    inconsistent state. The following validation errors have occurred:
    WARNING: The value of property 'RecipientTypeDetails', 536870912, is not
    defined in the Enum type 'RecipientTypeDetails'.

    can someone please help

    Thanks

    Thursday, March 6, 2014 3:38 AM

Answers

  • some extra research showed the solution

    this warning can be ignored, its generated because the discovery search mailboxes (part of exchange 2013) is not identified in exchange 2007 (in other word exchange 2007 doesn't know it does exit) so this is why this warning shows up

    run the get-mailbox on the exchange 2013 and this mailbox want generates any warning

    refer to the video below

    Thursday, March 6, 2014 3:48 AM

All replies

  • some extra research showed the solution

    this warning can be ignored, its generated because the discovery search mailboxes (part of exchange 2013) is not identified in exchange 2007 (in other word exchange 2007 doesn't know it does exit) so this is why this warning shows up

    run the get-mailbox on the exchange 2013 and this mailbox want generates any warning

    refer to the video below

    Thursday, March 6, 2014 3:48 AM
  • Hi,

    Thanks for your sharing. Besides that, I would like to make sure that there's no error on Exchange 2013, since we would migrate from Exchange 2007 to Exchange 2013 and this error on Exchange 2007 can be ignored.

    Best regards,
    Belinda


    Belinda Ma
    TechNet Community Support

    Friday, March 7, 2014 5:06 AM
    Moderator