Hi all,Had a fully working Exchange 2007 Enterprise installation since Feb. It's a single installation on a Windows 2003 Server R2 Enterprise x64 box. E.G. All roles are installed on the single box for Exchange. We have 3 DC's in the site, and a remote AD site used for just DR purposes that has a DC there too.We've had a couple of new starters in the past few weeks and i've noticed that these new mailboxes are not listed in the address book within Outlook 2007. However they appear fine in the address book when using OWA.After a bit of investigation, I am getting the following error within event viewer application log when the OAB updates (manually or on the schedule):Source: MSExchangeSACategory: OAL GeneratorEvent ID: 9330OALGen encountered error 80040115 (internal ID 500044c) accessing Active Directory DC01 for ''. - /o=mycompany/cn=addrlists/cn=oabs/cn=Offline Address Book From what I gather, this indicates an issue with communicating with AD. I've checked manually on the DC's and they all seem fine. I can see the Offline Address Book object within AD using ADSIEdit.msc, and after running the various troubleshooting tools within Exchange 2007 it's all coming back with a clean bill of health.There are no other known problems with this Exchange setup. Ihave enabled 'Expert' logging on the OAL Generator category, but I don't get anything additional in event viewer. Also, when I created the new OAB I had a look with ADSIEdit - yep, it's there in AD alright. On top of that I can also see in the event viewer various information entries that confirm that it's talking to AD fine. (E.G. a list of all DC's on the network etc.)Finally, I also tried running the update command from the EMS with verbose results turned on. Everything came back without a problem...This is pretty much as far I've got. I've tried creating a new OAB, setting as default etc - but no joy.I can see NOTHING wrong with our AD. No other issues have been reported with Exchange or the network in general - so i'm at my wits end.I have NOT got SP1 installed (still in beta I believe) and i've tried the usual reboot too! Any help appreciated!!!Cheers, Steve.

Came across this same issue working in a pre-SP1 environment. Someone had built the public folder database while the Exchange server was incorrectly using a DC/GC in another domain (but same site.)Fixed the issue so that Exchange server only used same site/same domain DC/GCs and then deleted and rebuilt the public folder database.Fixed issue.Key Point:/o=mycompany/cn=addrlists/cn=oabs/cn=Offline Address Book - is the directory structure in the Public Folder Database...not in the Active Directory.Hope that helps.

How did you set the Exchange server to only use a DC in the same site/domain?

hi there, i know this was an issue long time ago but just wonering how did you manage to force the PF to look at a particular DC? I am having similar issues, have a Root domain (which is empty) and another domain with the same forest which has exchange. have the simialr error as you had and the DC which is its looking at is in the root domain. any help will will be appreciated. thanks