Hi, I notice there is two MSExchangeSA event log error on our Exchange server. The event ID is 9325, Source is MSExchangeSA. Task Cat: OAL Generator.General detail: OALGen will skip entry 'Tom Smith' in address list '\Global address list' because the SMTP address '' is invalid- Default Offline Address Book.Now,'Tom Smith' is actualy an AD account without email enabled. So from my understandingit should not be included in OAL anyway. I've tried remove the Default OAL and re-created it. But still getting the same error. Any suggestions?

Was it mail(box) enabled earlier? Look like some of the mandatory attributes, for mail/mailbox enabled account, are having values set. You can verify mandatory and optional attributes (you can find list in below KB) of Tom Smith user account with ADSIEdit.msc and remove the values if you see anything. Wait for sometime or restart System Attendant service and check the behavior. Creating Exchange Server mailbox-enabled and mail-enabled objects in Active Directory http://support.microsoft.com/kb/275636 If above procedure doesn't resolve the issue then create a mailbox for user Tom Smith, wait for some time and remove mailbox, this should remove the attribute values... Amit Tank | MVP - Exchange | MCITP:EMA MCSA:M | http://ExchangeShare.WordPress.com

Hi aha_tom, From your post, it seems that this accounts attribute goes wrong, such as LegacyExchangeDN. In order to better troubleshoot the issue, please help to collect the following information: 1. Download OABInteg tool from the following link and install on your client, run the following command: http://code.msdn.microsoft.com/oabinteg/Release/ProjectReleases.aspx?ReleaseId=726 OABInteg /s:ExchSrvrName /t:proxytest /v:2 /l Note: replace ExchSrvrName with your actual Exchange servers name. 2. Locate the OABInteg.txt file under the root directory of C:, check whether you can see error information about the user, if so, please post it into the forum for analyze. I also found an article about 9325 error, for more information about it, please refer to the following article: Event ID 9325 is logged when Exchange 2003 generates an offline address list http://support.microsoft.com/default.aspx?scid=kb;EN-US;926206 For more information about OABInteg, please refer to the following article: Description of the Offline Address Book Integrity (OABInteg) tool http://support.microsoft.com/kb/907792/ If anything is unclear, feel free to let me know. Regards, Rock WangRock Wang MSFT

Guys,Removed the Exchange attributes as mentioned in the kb doesn't fix the error. But I found the user object attribute that causes the OAL error. It is called "ShowInAddressBook". Clear the value then update the OAL. No error!Thanks for all the helpful replies.

...And your answer - a year later - solved my problem also! I had a number of non-mail enabled system users that were always showing up in the Outlook OAL Generator event 9325. These are system users that have never had a mailbox nor ever will need one. Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9325 Date: 5/11/2010 Time: 3:15:34 PM User: N/A Computer: MAILMAN Description: OALGen will skip user entry 'XeroxCopier' in address list '\Global Address List' because the SMTP address '' is invalid. - Default Offline Address List I put "Exchange Attributes" on them and their errors went away when I rebuilt the Offline address book! The problem was that when I later deleted their mailbox and then removed their Exchange Attributes, the 9325 error returned. I figured that would clear everything, but apparantly not. I ran ADSI Edit on the user as aha_tom suggested and I found the name under an abandonded list in the "ShowInAddressBook" user object attribute. Instead of clearing the attribute on each user, I discovered that they were all pointing to an unused distribution list found in Org\Site\Recipients\All Global Address Lists\{listname} I deleted the abandonded address list found under "All Global Address Lists" and the errors on all of those user-ID's went away. The "oabinteg /s:mailman /t:proxytest /v:2 /l " test no longer shows anything either: Total number of temp legacyExchangeDN's found: 0 Why the errors in the first place? I'll never know, but perhaps this was a "leftover" from an old Exchange 5.5 to Exchange 2003 AD Connector. Stu

Thought I'd add my experience as well. We were seeing this on our Exch2007 server. We turned up logging and found that there were 6 addresses failing to update.We used OABInteg to get more info and all it did was confirm what Event Viewer was telling us. The fixes were varied. Some old accounts no longer had Exchange mailboxes and we were able to delete the accounts.Some we needed but ended up removing their ProxyAddresses in ADSIEdit, clicking Apply and adding them again into their mailbox using the EMC. Finally, for one we still had it listed as Legacy Mailbox. We ran -ApplyMandatoryAttributes on that mailbox and that one cleared up.