Hi thereI am running Exchcange 2007 SP1 on a 2003 Server SP2Ok i have noticed that people with cache mode are not getting the updates to their address books.I have looked into this and found I am getting errors on exchange 2007 of ID 9373 ID 9328 ID 9369I have tried the fix of http://support.microsoft.com/kb/931744but this has not worked.The error about HD full i cant see this beingcorrect as i have plenty of space.Any help on this would be great.Thanks in advanceLuke

Check below article and see if it solves your OAB issue. Mostly you need to rebuild OAB as content is corrupted shown in 9373... OAB Generation logs an Event ID 9373 when you update the offline address book in Exchange Server 2007 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 Exchange 2007 OAB Generation fails with the following errors: 9369, 9328 and 9328 http://blogs.msdn.com/dgoldman/archive/2008/12/17/exchange-2007-oab-generation-fails-with-the-following-errors-9369-9328-and.aspx Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hi AmitI have already tried the rebuild of the OAB but still get the same problem.You thinking by doing theExchange 2007 OAB Generation fails with the following errors: 9369, 9328 and 9328 that can fix 9373 error?The address book that is failing is the Default offline address list and as i understand it from that post you removing this and creating a new one?CheersLuke

Ok i have removed the default address book and created a new one and linked it to the GAL. I have done update and all the errors have gone so thats good news. ProblemI see now is when you do an update on a outlook 2003 client that is using cache modeI get a error(0x8004010F) An object could not be found.If i turn off cache mode then remove the OAB then turn cache mode back on it downloads ok with no errors and i can see the address that were missing, but if i do an update again same error.Any ideas?ThanksLuke

Ok problem is now fixed. I used this to solve it.http://support.microsoft.com/default.aspx/kb/905813