HiWe're having problems with our Exchange 2007 offline address book. Initially it just wasn't updating, and so the original OAB was deleted and a new one (with a different name) created. The creation worked fine, however when it tries to update we see eventid 9328 (category 13) OALGen encountered file error 80070020 (internal ID 50505c1) while generating the offline address list for address list '\\LDS-MAIL-STORE\ExchangeOAB\425759ec-f281-495c-9cdb-e120ac6a42e0\oab.xml'. Make sure there is enough disk space available. - test_oab_2We're running SCR, and there was a fix listed for this in Update Rollup 5 however we we've since patched to SP2 and issues persist. We have 2x Server 2003 R2 servers running Hub, CAS and Mailbox roles and 4 Server 2008 machines, 2 running Hub and CAS, 2 running Mailbox. There's a Server 2008 Edge Transport box, but I doubt that's relevant.Any suggestions will be gratefully received!EDIT - I should probably point out that there's a few Gib of space available on the disk - I'm not *that* slow ;)

Have you seen?:http://blogs.msdn.com/dgoldman/archive/2008/12/17/exchange-2007-oab-generation-fails-with-the-following-errors-9369-9328-and.aspx

Hi, The error 80070020 means that the process cannot access the file because it is being used by another process. At this time, I suggest you disable Anti-virus software on the Mailbox server which is responsible for generate the OAB files and generate OAB files again to check whether the issue still persists. If the issue could be solved, please refer to following article to exclude the directory from scanning by the Anti-virus software: File-Level Antivirus Scanning on Exchange 2007 http://technet.microsoft.com/en-us/library/bb332342.aspx Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Hi, Any updates?Thanks,Mike

Apologies for the delay in response - I've been snowed under! I'll be checking the AV setup over the weekend, will come back to you with some more info on Monday. Cheers for the suggestion!

Hokay - I set the exceptions as described in the link (all bar the IIS system files and the TMP directory were already exempt) and tried again - same proble. To completely rule out the antivirus (McAfee VirusScan Enterprise 8.7.0, if it's relevant) I totally uninstalled and then rebooted the server, but the same issue persists.Any idea what else could be locking the files?EDIT - it seems that the issue is something to do with web-based distribution. If I create the OAB for public folder distribution I seem to be able to update it numerous times fine. As soon as I set it to web-based distribution as well this error occurs.

Hokay - I set the exceptions as described in the link (all bar the IIS system files and the TMP directory were already exempt) and tried again - same proble. To completely rule out the antivirus (McAfee VirusScan Enterprise 8.7.0, if it's relevant) I totally uninstalled and then rebooted the server, but the same issue persists.Any idea what else could be locking the files?EDIT - it seems that the issue is something to do with web-based distribution. If I create the OAB for public folder distribution I seem to be able to update it numerous times fine. As soon as I set it to web-based distribution as well this error occurs. Any help from the link I posted earlier?http://blogs.msdn.com/dgoldman/archive/2008/12/17/exchange-2007-oab-generation-fails-with-the-following-errors-9369-9328-and.aspx

Sadly not Andy - I'd already tried that :(

Download Process Monitorfromhttp://technet.microsoft.com/en-us/sysinternals/bb896645.aspxand manually rebuild the OAB and see if you can see what process is locking those files.

Hi, Firstly, I would like to explain the process that OAB files are generated by mailbox server: 1. A system attendant profile needs to be created before an Offline Address Book can be generated 2. After the profile has been created, DSAccess is called by mad.exe for initial information 3. OABGen will query the active directory via NSPI 4. OABGen creates the local distribution point 5. OABGen will write the files to the respective locations and depending upon the OAB distribution: i.e. Public folder Distribution and Web based distribution Local distribution point mentioned on step No 4. can be different. For Public folder Distribution it is Windows Temp directory. For Web based distribution it is ExchnageOAB shared folder. Therefore, for your issue, I still think the issue occurs as some processes which lock the ExchnageOAB shared folder. I agree with Andy that you use Process Monitor to check which process is locking the files. Mike Shen TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com

Good stuff - that would explain why things fail on web based distribution rather than PF. I'll give Process Monitor a whirl and come back to let you know either way.

I'm not quite sure what I'm looking for here - I've applied a filter so that only processes and events affecting the ExchangeOAB directory, but I'm not seeing anything pertaining to locks or access denied. Interestingly enough the entry for eventID9328 (the "out of disk space" error) occurs 2 seconds after the last entry pertaining. Am I limiting my filter too much?The processes related to the generation of the OAB files seem to be mad.exe and... that's about it. When the generation is run for web-based distribution (ie the failing attempts) I'm seeing a number of "FAST IO DISALLOWED" - there seems to be one for each .lzx entry. When the generation runs for PF based distribution only these entries don't seem to exist.

I'm not quite sure what I'm looking for here - I've applied a filter so that only processes and events affecting the ExchangeOAB directory, but I'm not seeing anything pertaining to locks or access denied. Interestingly enough the entry for eventID9328 (the "out of disk space" error) occurs 2 seconds after the last entry pertaining. Am I limiting my filter too much?The processes related to the generation of the OAB files seem to be mad.exe and... that's about it. When the generation is run for web-based distribution (ie the failing attempts) I'm seeing a number of "FAST IO DISALLOWED" - there seems to be one for each .lzx entry. When the generation runs for PF based distribution only these entries don't seem to exist. Not sure you have tried these other suggestions from Dave yet: ( this is a different link)http://blogs.msdn.com/dgoldman/archive/2008/12/16/oab-generation-logs-an-event-id-9373-when-you-update-the-offline-address-book-in-exchange-server-2007.aspx

I'm not quite sure what I'm looking for here - I've applied a filter so that only processes and events affecting the ExchangeOAB directory, but I'm not seeing anything pertaining to locks or access denied. Interestingly enough the entry for eventID9328 (the "out of disk space" error) occurs 2 seconds after the last entry pertaining. Am I limiting my filter too much?The processes related to the generation of the OAB files seem to be mad.exe and... that's about it. When the generation is run for web-based distribution (ie the failing attempts) I'm seeing a number of "FAST IO DISALLOWED" - there seems to be one for each .lzx entry. When the generation runs for PF based distribution only these entries don't seem to exist. Not sure you have tried these other suggestions from Dave yet: ( this is a different link)http://blogs.msdn.com/dgoldman/archive/2008/12/16/oab-generation-logs-an-event-id-9373-when-you-update-the-offline-address-book-in-exchange-server-2007.aspx Thanks again Andy. Just to clarify something from that blog entry: it suggests that AV on the CAS can cause an issue with the generation of the OAB. If my understanding is correct then the web-based distribution point is created on the mailbox server, then these files are copied by the CAS server (by way of FDS). If this is the case then how can AV running on the CAS cause the creation of the local distribution point on the mailbox server to fail?Permissions are correct according to that article though - the ExchangeOAB share on the MB server has Administrators and System with Full Control, Exchange Servers has List Folder and Read permissions.Disk issues are unlikely as the servers are virtualised, storage on a VMFS3 volume on a NetApp SAN. If there are disk issues with the underlying hardware I'd expect the SAN to flag these.The rest of that link seems to be basically telling me to recreate and update the OAB: I've done this numerous times already :(To reiterate - Public Folder distribution is fine, as soon as web-based distribution is enabled I get the error regards no disk space being available. This entry is in the log of the mailbox server generating the OAB, not on the CAS server.

Can you generate the OAB on another server?

The OAB was originally generated on one of the Server 2003 R2 boxes, we moved from that to one of the 2008 servers in an attempt to resolve this, so I'm afraid that the issue doesn't seem to be restricted to this particular server.

Anyone else got any thoughts on this? Public Folder distribution is still working fine, the issues only start when we set distribution to be web based. We're looking to move to Outlook 2007 and kill off our Public Folders, so it'd be good if we could get this working :)

This is a tough one for sure. Would it be possible to bring up a temporary, new server and move the OAB generation to it as a test? ( One that isnt a virtual image?)Any disk quotas enabled on the drives?

I had the exact same issue mate - but turns out it was because of the shared cluster folder I was using. I had ExchangeOAB on a shared folder on a cluster. Whoever was here before me had setup the folder wrong – they just created a new folder on a clustered drive and shared it. It looked ok in the cluster administrator, but only the one node where it was created had access to it. Whenever it failed over to the other node Exchange could not access the ExchangeOAB folder therefore no OAB was created and the system kicked out the same error you posted above.