none
event id 9327 OALGen skipped some entries in the offline address list RRS feed

  • Question

  • Getting an warning in the event viewer every time OAL Generator runs. The problem is that  diagnostic logging for OAB shows an AD account that does not even have a mailbox.  How can it get pulled in to the GAL if it does not even have an email?

    OALGen skipped some entries in the offline address list '\Global Address List'.  To see which entries are affected, event logging for the OAL Generator must be set to at least medium.

    - Default Offline Address List

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Thursday, November 14, 2013 6:45 PM

Answers

  • Hi,

    Based on my research, this Warning event is logged when Microsoft® Exchange Server cannot download one or more entries of an offline address list. You can learn more about the root cause of this error by examining the Application log for related events.

    To resolve this error, do one or more of the following: (assume it is Exchange 2003)

    • Increase diagnostic logging, and then examine the event log for MSExchangeSA events that are logged before and after MSExchangeSA event 9327.

    To increase diagnostic logging:

    1.In Exchange System Manager, double-click Servers, right-click a server, and then click Properties.

    2.On the Diagnostic Logging tab, under Services, select MSExchangeSA.

    3.In Categories, click OAL Generator.

    4.In Logging level, select Maximum.

    • Use the Offline Address Book Integrity (OABInteg) tool to diagnose and resolve generation issues. Active Directory®-related issues, such as replication problems, latency, and stale information, can frequently cause the OAB file generation process to fail. You can use the OABInteg tool to scan Active Directory for these types of issues. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

    Regards,


    Rebecca Tu
    TechNet Community Support

    Friday, November 15, 2013 3:13 PM

All replies

  • Check the "mail" attribute on that AD object. It's probably populated with an e-mail address. If you don't like the events in your log then clear that property unless the objects is also mail-enabled in Exchange.

    If you want the details, follow the instructions in the event log and increase the logging level.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, November 14, 2013 10:30 PM
  • The problem is that  diagnostic logging for OAB shows an AD account that does not even have a mailbox
    Friday, November 15, 2013 12:29 AM
  • Hi,

    Based on my research, this Warning event is logged when Microsoft® Exchange Server cannot download one or more entries of an offline address list. You can learn more about the root cause of this error by examining the Application log for related events.

    To resolve this error, do one or more of the following: (assume it is Exchange 2003)

    • Increase diagnostic logging, and then examine the event log for MSExchangeSA events that are logged before and after MSExchangeSA event 9327.

    To increase diagnostic logging:

    1.In Exchange System Manager, double-click Servers, right-click a server, and then click Properties.

    2.On the Diagnostic Logging tab, under Services, select MSExchangeSA.

    3.In Categories, click OAL Generator.

    4.In Logging level, select Maximum.

    • Use the Offline Address Book Integrity (OABInteg) tool to diagnose and resolve generation issues. Active Directory®-related issues, such as replication problems, latency, and stale information, can frequently cause the OAB file generation process to fail. You can use the OABInteg tool to scan Active Directory for these types of issues. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

    Regards,


    Rebecca Tu
    TechNet Community Support

    Friday, November 15, 2013 3:13 PM
  • That's correct. If the "mail" attribute doesn't match the primary SMTP proxy address in the proxyAddresses property of the user (maybe because there is no such attribute in the user's properties) the error is recorded. So have a look at that user and if it doesn't have a mailbox but it has a populated mail attribute, clear the mail attribute and the error will disappear.

    --- Rich Matheisen MCSE&I, Exchange MVP

    Friday, November 15, 2013 10:46 PM