A large number of users in one of our Exchange 2010 environments (the users have only just started using this new environment) reported that out of office was not working so after a bit of diagnostics, removing any mailbox rules, restarting the mailbox assistant service I then attempted to move the users to a different mailbox database. However the move fails with MapiExceptionBadValue: Unable to synchronize manifest. A 'consultant' migrated the users from an Exchange 2003 environment in a different but left little information on what tools/method he used. 

After seeing this before I thought a mailbox repair would work but the same error occurs on attempting to move. The command I used incorporated all of the corruption types I'm aware of - SearchFolder, AggregateCounts, ProvisionedFolder, MessagePtagCn, MessageId. It completes very quickly with no errors in event viewer.

Apart from creating a new mailbox and running an export/import has anybody got any suggestions?

Hi,

Does this issue occur on one specific mailbox?

Try using the MFCMAPI and deleted the IPM.Rule.Message, IPM.Note.Rules.OofTemplate and IPM.Note.Rules.ReplyTemplate message classes from the user mailbox.

http://mfcmapi.codeplex.com/

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Hi,

So far I've had reports that OOF is not working on 20 mailboxes out of 400 but these will only be people that have put it on so far or who have been informed that no message was sent. More importantly as a test I've attempted to move 30 mailboxes - 10 of which have the same error.

I'll attempt to use MFCMAPI once I find a server to put install CDO on as I have no access to the user's PCs.

If this works on one mailbox any suggestions on how to perform this on mass?

Thanks.