[Today’s post comes to us courtesy of Mohammed Sabir and Shammi Dua from Commercial Technical Support]
When migrating to Small Business Server 2011, you may experience Public Folder Replication failures and users unable to send mail to mail enabled Public Folders.
In an environment where Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 previously existed, and all those servers have been removed during migration, there is a chance that an Administrative Group (First Administrative Group or another custom Administrative Group) remains with a Servers container, but no servers inside it.
During Public Folder replication, when the Exchange 2010 Store Driver sees the empty Servers container in Active Directory, it expects a System Attendant object inside the container and when it is not found, the following error is logged in the events:
Source: MSExchange Store Driver
Event ID: 1020
The store driver couldn’t deliver the public folder replication message “Hierarchy (PublicFolder@contoso.com)” because the following error occurred: The Active Directory user wasn’t found.
In addition to above behavior, you may experience issue wherein you cannot send email to mail enabled public folders and receive an NDR as follows:
“#554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory user wasn’t found. ##”
Scenarios in which above behaviors can be seen:
In above scenarios, the Servers Container in Administrative Group (First Administrative Group or another custom Administrative Group from Exchange 2003) is left empty.
To resolve this issue, follow these steps:
Warning: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall the Windows Server Operating System or Microsoft Exchange or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.