Mailboxes are not processed by the Mail Source Agent (MSA) and an error similar to the following is noted in the EMWMSA.log:
"CMBMConn::CheckHomeServer Warning 4814 Mailbox /o=OrgName/ou=SiteName/cn=Recipients/cn=MailboxName has wrong home server."
See resolution.
View the affected source object detailed in the log using ADSIEdit to check that it's msExchHomeServerName and homeMDB attributes are correct and that they dont have any hidden preceding or trailing spaces.
This error has also been observed where the mailbox store in Exchange 2007 does not have its display name populated. To check this do the following:
From the Start menu, select Run; and in the Run dialog type ADSIEdit.msc and click OK. (ADSIEdit utility is a part of the Windows 2000/2003 Support Tools. To install the Support Tools run the SupportToolsSuptools.msi file located on the Windows 2000/2003 CD.)
In the ADSIEdit snap-in, connect to the Configuration (Select a well known Naming Context: drop down box) and browse to the <CN=Configuration,DC=Target_Domain,DC=com>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=<ExchangeOrganizationName>, CN=Administrative Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Servers, CN=Server_Name, CN=InformationStore, CN=<StorageGroupName>.
Then right-click on the mailbox database in the right-hand pane and select Properties. If the database does not have the displayName attribute set then copy the value from the adminDisplayName attribute to the displayName.
Another issue that has been noted to cause the warning message is when the object hasn't been processed by directory synchronization. Check extension-attribute-15 (by default) of the target mailbox as it should contain the objectGUID of the corresponding matched source mailbox. Makesure the object is within the directory synchronization scope (look on the Active Directory Synchronization tab, then view the Directory Migration, Synchronization properties). If the object hasn't been picked up by the directory synchronization job then a directory re-sync may be needed (right-click the Synchronization job and select Start and Re-Sync).
The displayName process is fully documented within the Migration Manager for Exchange Quick Start guide, and is a prerequisite to the software deployment.
The warning has been observed with the source server in an Exchange 2007 to Exchange 2007 migration. It was quickly identified after a re-enumerated the source org. At the end of the re-enumeration a pop-up message came back stated that one of the mailbox databases was not named.
In addition, the EMWMSA.log file contains the following for a normal working mailbox at start of processing:
CADQueue::NextItem Informational 4511 Starting to process item /o=OrgName/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=MailboxName (Collection Collection1, PST: 2589EFA6AC155A429E106510CBA5BECA, SyncMailboxInfo: True, SyncSwitched: False, SyncAllContent: False, SyncFolderContent: False).
A mailbox with a database name problem looks like this at start of processing:
CADQueue::NextItem Informational 4511 Starting to process item /o=OrgName/ou=First Administrative Group/cn=Recipients/cn=MailboxName (Collection Fix, PST: 510A5DE0F0AF9A41A3E5BF1289610A7F, SyncMailboxInfo: True, SyncSwitched: False, SyncAllContent: True, SyncFolderContent: True).
Which returned this warning, CMBMConn::CheckHomeServer Warning 4814 Mailbox /o=OrgName/ou=First Administrative Group/cn=Recipients/cn=MailboxName has wrong home server.
Notice the difference in the legacyExchangeDN. The second mailbox was on the same E2K7 server as the first mailbox, but it was on a database that did not have the displayName set.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center