Topic Last Modified: 2010-04-26

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

9321

Event Source

MSExchangeSA

Alert Type

Warning

Rule Path

Microsoft Exchange Server/Exchange 2010/Mailbox/System Attendant

Rule Name

The OABGen couldn't generate full details because the total size of the details information is greater than 64 KB.

Explanation

This Error event indicates that the full details for user %1 in offline address book (OAB) %2 will be truncated because the size of a specific attribute exceeds the default limit of 64 kilobytes per attribute. This error is typically associated with users who have an abnormally large list of e-mail proxy addresses or e-mail certificates.

User Action

To resolve this error, use the following list of attributes to examine the properties of the user specified in the error and determine which attribute is causing the error. After the attribute has been identified, perform one of the following two options to resolve the error:

  • Reduce the number of items in the attribute by removing them from the user object in Active Directory.

  • Change the maximum size limit for the specific attribute. For more information about identifying the attribute that caused the error and making a registry change to resolve the error, see MSDN blog article OAB Property filtering for Exchange 2003 Service Pack 2 OAB Version 4.

    Note:
    The content of each blog and its URL are subject to change without notice.

The following list contains the attributes in a limited OAB when there has been no full download:

  • PR_EMAIL_ADDRESS_A

  • PR_DISPLAY_NAME_A

  • PR_OFFICE_LOCATION

  • PR_ACCOUNT_A

  • PR_SURNAME_A

  • PR_SMTP_ADDRESS_A

  • PR_SEND_RICH_INFO

The following list contains the attributes included in a full details OAB, in addition to the seven attributes that are included in a limited OAB. The last two properties are in addition to the Unicode OAB.

  • PR_USER_CERTIFICATE

  • PR_USER_X509_CERTIFICATE

  • PR_EMS_AB_X509_CERT

  • PR_BUSINESS_TELEPHONE_NUMBER_A

  • PR_GIVEN_NAME_A

  • PR_INITIALS_A

  • PR_STREET_ADDRESS_A

  • PR_LOCALITY_A

  • PR_STATE_OR_PROVINCE_A

  • PR_POSTAL_CODE_A

  • PR_COUNTRY_A

  • PR_TITLE_A

  • PR_COMPANY_NAME_A

  • PR_ASSISTANT_A

  • PR_DEPARTMENT_NAME_A

  • PR_BUSINESS_TELEPHONE_NUMBER_A

  • PR_HOME_TELEPHONE_NUMBER_A

  • PR_BUSINESS2_TELEPHONE_NUMBER_A

  • PR_HOME2_TELEPHONE_NUMBER_A

  • PR_PRIMARY_FAX_NUMBER_A

  • PR_MOBILE_TELEPHONE_NUMBER_A

  • PR_ASSISTANT_TELEPHONE_NUMBER_A

  • PR_PAGER_TELEPHONE_NUMBER_A

  • PR_COMMENT_A

  • PR_EMS_AB_PROXY_ADDRESSES

  • PR_EMS_AB_TARGET_ADDRESS

  • PR_EMS_AB_HOME_MDB_A

  • PR_EMS_AB_HAB_SENIORITY_INDEX

  • PR_EMS_AB_IS_ORGANIZATIONAL

  • PR_EMS_AB_OBJECT_GUID

  • PR_EMS_AB_DL_SENDER_HINT_TRANSLATIONS_W

  • PR_EMS_AB_DELIV_CONT_LENGTH

  • PR_EMS_AB_ENABLE_MODERATION

  • PR_EMS_AB_DL_TOTAL_MEMBER_COUNT

  • PR_EMS_AB_DL_EXTERNAL_MEMBER_COUNT

Be aware that the OAB does not contain custom properties in the directory that an administrator has added, such as employee ID, organizational hierarchy information, or group membership information. Outlook needs access to the server to be able to retrieve this information.

Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and others. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to review your organization's guidelines first.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.