-
Title
Warnings In Custom Recipients, or Mail Enabled Objects Gathering Task: "object could not be store -
Description
When Running the Exchange Mail Eabled Objects, or Custom Recipients gathering tasks warnings are presented stating that One or More Objects could not be stored in the database as they do not contain all the required attributes:
The following Custom Recipient object could not be stored in the database as it did not have the minimum required properties: CN=UserName; DN=; X500DN=CN=UserName,OU=OUName,DC=Domain,DC=com -
Cause
The Object referenced in the warning message may be missing the DistinguishedName, or LegacyExchangDN attributes.
-
Resolution
Investigate the attributes listed in the warning message. The Three Database fields are Labled CN, DN, and X500DN. These Attributes Reference CN, LegacyExchangeDN, and distinguishedName AD Attributes respectively. Each Attribute in the Warning Message is separated by a semicolon (;)
The Following Example would be presented if a Custom Recipient Object did not able a LegacyExchangeDN attribute populated within Active Directory (Note the DN field is NULL, indicating the the LegacyExchangeDN attribute in AD is not populated correctly for this object):
The following Custom Recipient object could not be stored in the database as it did not have the minimum required properties: CN=UserName; DN=; X500DN=CN=UserName,OU=OUName,DC=Domain,DC=com