OAB errors
Hi All,
I have the problem that the OAB is not genarating the Address Book. It looks like a security issue, because the machine is on, and reachable.
Some info:
The servers prc19n01 and prc19n51 are the domain controllers from the root domain.
Exchange 2007 SP1 - rollup 9
Generation server is one (of 2) HUB/CAS/MBX (only public folders) servers.
3 Mailbox CCR's
We get the following errors (information) in the eventlog
Eventid: 2090
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2016). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
prc19n01.root.xx CDG 0 0 0 1 0 0 0 0 0
prc19n02.directory.xx CDG 1 7 7 1 0 1 1 7 1
prc19n51.root.xx CDG 0 0 0 1 0 0 0 0 0
prc19n52.directory.xx CDG 1 7 7 1 0 1 1 7 1
prc19n53.directory.xx CDG 1 7 7 1 0 1 1 7 1
prc19n03.directory.xx CDG 1 7 7 1 0 1 1 7 1
Out-of-site:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Tried to move the OAB generation server, still getting the following errors.
Event Type: Error
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9334
Date: 6/24/2010
Time: 8:59:06 AM
User: N/A
Computer: PRC559N21
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=<orgname>/cn=addrlists/cn=oabs/cn=Offline Adres 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: 9330
Date: 6/24/2010
Time: 8:59:06 AM
User: N/A
Computer: PRC559N21
Description:
OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory PRC19N01 for ''.
- /o=<orgname>/cn=addrlists/cn=oabs/cn=Offline Adres List
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
[PS] C:\Documents and Settings\ps_e60456>Get-ExchangeServer -Status | fl identity,*exclu*
Identity : PRC559N05
StaticExcludedDomainControllers : {}
Identity : PRC559N55
StaticExcludedDomainControllers : {}
Identity : PRC559N71
StaticExcludedDomainControllers : {prc19n01.root.xx, prc19n51.root.xx}
Identity : PRC559N21
StaticExcludedDomainControllers : {prc19n01.root.xx, prc19n51.root.xx}
Identity : PRC559Q71
StaticExcludedDomainControllers : {prc19n01.root.xx, prc19n51.root.xx}
Identity : PRC559Q15
StaticExcludedDomainControllers : {prc19n01.root.xx, prc19n51.root.xx}
Identity : PRC559Q14
StaticExcludedDomainControllers : {prc19n01.root.xx, prc19n51.root.xx}
(The prc559n05 and prc559n55 are Exchange 2003 servers, used for legacy applications)
Where to start resolving this problem?
If have been searching, and found a couple of articles, but non of them seems to apply here, in a root/child configuration.
June 24th, 2010 10:39am
Hi ,
Please try these steps I hope it will resolve your problem.
1. Stop and Start the DNS Server Services on the GC and The DC machines.
2. On the Exchange Server, where does the DNS entry point to ?
Change the Primary to point to an AD integrated DNS or another GC in your organization within the same IP Site.
3.Set all Exchange services to stop and manual.
4.Open - Properties, DSACCESS, and uncheck the Automatic checkbox
5.Add the DC and The GC's Manually
6.apply and restart the server
7.ipconfig/flushdns and ipconfig/registerdns
8.before you start the Exchange services, on the GC's click on DNS Server properties and choose clear cache
9. Nslookup yourdomain.com should point to all IPaddresses of your GC's n DC's.
10. On Exchange Server start the DNSClient and DHCPClient service, Server Service.
11. Start exchange services manually
12. Flush the cache by typing this on the command prompt
Net Stop Resvc
Net Stop SMTPSvc
Net Start SMTPSvc
Net Start Resvc
The logs must be clear of this errors now...!
Regards.
Shafaquat Ali.
M.C.I.T.P Exchange 2007 M.C.I.T.P Windows Server 2008 M.C.T.S OCS Server 2007 R2
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2010 10:50am
Am Thu, 24 Jun 2010 07:39:53 +0000 schrieb fvanloon:
> Hi All,
>
> I have the problem that the OAB is not genarating the Address Book. It looks like a security issue, because the machine is on, and reachable.
>
> Some info:
> The servers prc19n01 and prc19n51 are the domain controllers from the root domain.
> Exchange 2007 SP1 - rollup 9
>
> Generation server is one (of 2) HUB/CAS/MBX (only public folders) servers.
> 3 Mailbox CCR's
>
> We get the following errors (information) in the eventlog
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Tried to move the OAB generation server, still getting the following errors.
>
> Event Type: Error
> Event Source: MSExchangeSA
> Event Category: OAL Generator
> Event ID: 9334
> Date: 6/24/2010
> Time: 8:59:06 AM
> User: N/A
> Computer: PRC559N21
> 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=<orgname>/cn=addrlists/cn=oabs/cn=Offline Adres 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: 9330
> Date: 6/24/2010
> Time: 8:59:06 AM
> User: N/A
> Computer: PRC559N21
> Description:
> OALGen encountered error 80040115 (internal ID 50004ef) accessing Active Directory PRC19N01 for ''.
> - /o=<orgname>/cn=addrlists/cn=oabs/cn=Offline Adres List
> Where to start resolving this problem?
> If have been searching, and found a couple of articles, but non of them seems to apply here, in a root/child configuration.
>
Which article? Did you try this:
http://technet.microsoft.com/en-us/library/dd285503(EXCHG.80).aspx
best regards
Christian
June 24th, 2010 10:56am
Hi ,
Please try these steps I hope it will resolve your problem.
1. Stop and Start the DNS Server Services on the GC and The DC machines.
2. On the Exchange Server, where does the DNS entry point to ?
Change the Primary to point to an AD integrated DNS or another GC in your organization within the same IP Site.
* It is already pointing to a DC / GC in the same site (prc19n52)
3.Set all Exchange services to stop and manual.
4.Open - Properties, DSACCESS, and uncheck the Automatic checkbox
* Here i'm lost, what to open?
Free Windows Admin Tool Kit Click here and download it now
June 24th, 2010 11:08am
@ Christina,
I have seen this article, but I didn't apply to fix.
I have read it, in de understanding that the fix only applies when the CCR is creating the OAB.
In our situation the OAB is genarated by a HUB/CAS server which is not part of the CCR.
June 24th, 2010 11:26am
Hi fvanloon,
Did you view this article to troubleshoot it:
http://blogs.msdn.com/b/dgoldman/archive/2007/11/15/oab-generation-fails-to-generate-with-errors-9330-and-9334.aspx
Please check it and confirm whether can help you.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2010 12:09pm
I'll look in to it today.
Been away for some days..sorry for the late response.
July 1st, 2010 11:13am
Hi,
Thanks for your update.
Please try and post here if you have questions.
Thanks
Allen
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2010 5:37am
Problem is resolved, thanks to PSS
The root domain controllers couldn't be resolved based on the NETBIOS name.
We tried pinging them on IP-address and on the FQDN.
We added the DNS Suffix , and the machine could then be reached by the OAB process.
July 2nd, 2010 11:56am
Hi Fvanloon,
Thanks for your sharing.
How did you know the DC is the issue? If possile, could you share more information here?
John
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2010 3:55pm
Hi John,
The DC was not the problem, only the reachability of the DC was a problem. When we tried to ping the machine on a NETBIOS name, i could't be reached.
After adding the DNS suffix on the OAB generation server, the machine was reachable, and the OAB process was running fine.
July 6th, 2010 11:10am
Hi,
Thank you for sharing. That is indeed very helpful for the users.
Allen
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2010 12:22pm