Exchnage OAB not updating because of child domain controller.

I have a parent and child domain.  Exchange only runs in the parent domain.  I noticed in Exchange that it was picking up the child domain controller under Server Config, Server Properties, System Settings, Active Directory servers.  In that screen the two parent domain contrllers and one child domain controllers were listed.  This caused sporadic issues if the child domain DC was use for some Exchange related function.

I ran this command to exclude the child DC:

set-exchangeserver -identity "exchange server" -StaticExcludedDomainControllers:childdomain controller

Now the Offline Address Book is not updating.   I added a new user and noticed it was not appearing in the GAL.  If I turned off cached exchange mode it did appear.  It also appeatrs under Address Books, All Address Books, All users in either cached or non-cached.

The application event logs has two errors referecing the child DC:

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      OAL Generator
Event ID:      9330
Date:            3/1/2011
Time:            9:34:36 AM
User:            N/A
Computer:      
Description:
OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory CHILD DC for ''.
- /o=DOMAIN/cn=addrlists/cn=oabs/cn=Default Offline Address List

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      MSExchangeSA
Event Category:      OAL Generator
Event ID:      9334
Date:            3/1/2011
Time:            9:34:36 AM
User:            N/A
Computer:      
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=DOMAIN/cn=addrlists/cn=oabs/cn=Default Offline Address List

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

An thoughs on what is going in here and how to prevent it.  
LVL 14
dmwynneAsked:
Who is Participating?
 
dmwynneConnect With a Mentor Author Commented:
Turns out this was the child domain controller having routing and remote access enabled and two network cards.  I know that it is not recommended for a domain controller to be multi-homed but this is a  test domain so I didn't care.  I didn't realize exchange would interact with the child domain even though exchange is not running in that domain.  Turning off routing and remote access on the child domain controller fixed the issue.
0
 
Sudhirchauhan3Commented:
You may want to set "MSExchangeSA\OAL Generator" logging level to expert and share the logs here.
I suspect
This link matches exactly to your problem but is applicable for Exchange 2003 only.
http://support.microsoft.com/kb/905802

0
 
dmwynneAuthor Commented:
I set the logging but nothing much has shown up in events.

According to the article it references MSEMS_DSA_Admin section.  That section is not in the file.  Also the only place I found the file mapisvc.inf was under system\syswow64.
0
 
dmwynneAuthor Commented:
Found solution.
0
All Courses

From novice to tech pro — start learning today.