Hi Everyone. I am unable to get the offline address book to update. We are running Exchange 2007 service pack 3 rollup 1. We have just moved to a new datacenter and this is hopefully the last issue that is outstanding. When I run the OAB update I immediately get two erros in the event log on the mailbox server Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9330 Date: 11/01/2011 Time: 09:20:41 User: N/A Computer: PROD-MAILSV-001 Description: OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory 298320-PADDOM01 for ''. - /o=openwork/cn=addrlists/cn=oabs/cn=Default Offline Address Book Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9334 Date: 11/01/2011 Time: 09:20:41 User: N/A Computer: PROD-MAILSV-001 Description: OALGen encountered error 80040115 while initializing the offline address list generation process. No offline address lists have been generated. Please check the event log for more information. - /o=openwork/cn=addrlists/cn=oabs/cn=Default Offline Address Book The exchange server is in the root domain as are all of the users. When I look at what domain controllers Exchange is using it is showing the two domain controllers that are in the same domain as the Exchange server and no others. For some reason the OAB update seems to always want to use domain controllers that are in a child domain. This child domain is not Exhcange enabled as it doesn't contain any exchange servers or mail enabled objects. I have added the command to exclude the domain controllers in the child domain and rebooted the server but this hasnt effected the OAB generation. There is a firewall between Exchange and the domain controllers in the child domain but our networking guys can see the traffic between the mail server and the domain controllers and they are telling me that the communication looks as expected Has anyone got any suggestions on how to force OAB to the domain controllers in the same domain as Exchange? or as to what may be causing this problem? I have upped the diagnostic logging for OAB to expert.

To add to this. We have a DR mailbox server at another site that takes SCR copies from the main mailbox server. I moved the OAB to this server this morning and ran the update. Again the update failed and again the error shows the OAB failing to talk to a DC in the child domain. This time there is no firewall between Excahnge and the DC. Is anyone aware of any requirements that are needed on the child domain for this to work. I have checked the logs on the child domain domain controllers but not seeing any errors.

On Tue, 11 Jan 2011 09:54:11 +0000, Jon Warburton wrote: > > >Hi Everyone. I am unable to get the offline address book to update. > >We are running Exchange 2007 service pack 3 rollup 1. We have just moved to a new datacenter and this is hopefully the last issue that is outstanding. > >When I run the OAB update I immediately get two erros in the event log on the mailbox server http://blogs.msdn.com/b/dgoldman/archive/2007/11/15/oab-generation-fails-to-generate-with-errors-9330-and-9334.aspx Also, have you turned off IPv6? [ snip ] >The exchange server is in the root domain as are all of the users. When I look at what domain controllers Exchange is using it is showing the two domain controllers that are in the same domain as the Exchange server and no others. > >For some reason the OAB update seems to always want to use domain controllers that are in a child domain. This child domain is not Exhcange enabled as it doesn't contain any exchange servers or mail enabled objects. Are those DC/GC servers in the same AD site? If they are, there's no reason why the GCs shouldn't be used. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thank you for the reply. I had a look at the link that you suggested but didnt find anything that seemed to help with the issue. The Exchagne servers are Windows 2003 and dont have IPv6 The domain controllers in the child domain are in the same AD site

On Thu, 13 Jan 2011 10:38:48 +0000, Jon Warburton wrote: > > >Thank you for the reply. I had a look at the link that you suggested but didnt find anything that seemed to help with the issue. The link, in that case, is still useful since it points out that there's some sort of permission problem. Crank up the logging level on the OAB Generation and see if there's anything more useful in the Application log. >The Exchagne servers are Windows 2003 and dont have IPv6 > >The domain controllers in the child domain are in the same AD site Then any one of the GCs is as good as the other. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP