Hi, I don't know if it relates to the fact thatI removed a DC of subdomain a day before but I'm getting this err now:Event Type:ErrorEvent Source:MSExchangeSAEvent Category:OAL Generator Event ID:9360Date:11/19/2009Time:1:06:54 AMUser:N/AComputer:EXCHANGE01Description:OALGen encountered an error while generating the changes.oab file for version 2 and 3 differential downloads of address list '\Global Address List'. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OAL post full if diff fails' and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads. - Default Offline Address List

Hi Look at the fic for the error given in this Kbhttp://support.microsoft.com/kb/922255Looks like you need to do changes in the registry.Raj

Thanks but to be more specific, I get this errors: Event Type: Warning Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9341 Date: 11/19/2009 Time: 4:13:14 AM User: N/A Computer: EXCHANGE01 Description: The parent Legacy Exchange DN container value /o=Labtest/ou=Labo/cn=Recipients/cn=Depart was not found during generation of the differential update file for offline address list '\Global Address List'. This will force clients using this offline address list to do a full download of the offline address list. - Default Offline Address List For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9360 Date: 11/19/2009 Time: 4:13:14 AM User: N/A Computer: EXCHANGE01 Description: OALGen encountered an error while generating the changes.oab file for version 2 and 3 differential downloads of address list '\Global Address List'. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OAL post full if diff fails' and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads. - Default Offline Address List For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Warning Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9341 Date: 11/19/2009 Time: 4:13:14 AM User: N/A Computer: EXCHANGE01 Description: The parent Legacy Exchange DN container value /o=Labtest/ou=Labo/cn=Recipients/cn=Depart was not found during generation of the differential update file for offline address list '\Global Address List'. This will force clients using this offline address list to do a full download of the offline address list. - Default Offline Address List For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Error Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9360 Date: 11/19/2009 Time: 4:13:14 AM User: N/A Computer: EXCHANGE01 Description: OALGen encountered an error while generating the changes.oab file for version 2 and 3 differential downloads of address list '\Global Address List'. The offline address list has not been updated so clients will not be able to download the current set of changes. Check other logged events to find the cause of this error. If the cause of the problem was intentional or cannot be resolved, OALGen can be forced to post a full offline address list by creating the DWORD registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OAL post full if diff fails' and setting it to 1 on this server. When OALGen next generates the offline address list, clients will perform a full OAB download. After that time, the registry key should be removed to prevent further full downloads. - Default Offline Address List For more information, click http://www.microsoft.com/contentredirect.asp. Event Type: Warning Event Source: MSExchangeSA Event Category: OAL Generator Event ID: 9320 Date: 11/19/2009 Time: 4:13:19 AM User: N/A Computer: EXCHANGE01 Description: OALGen could not generate full details for some entries in the offline address list for address list '\Global Address List'. To see which entries are affected, event logging for the offline address list generator must be set to at least medium. - Default Offline Address List For more information, click http://www.microsoft.com/contentredirect.asp.

On Sun, 22-Nov-09 06:54:08 GMT, SAMATA wrote: [ snip ]>The parent Legacy Exchange DN container value ‘/o=Labtest/ou=Labo/cn=Recipients/cn=Depart’ was not found during generation of the differential update file for offline address list '\Global Address List'. This will force clients using this offline address list to do a full download of the offline address list. Have you removed an Exchange Administrative Group named "Depart"?Have a look at this:/dgoldman/archive/2005/11/18/OAB-PDN-Changes-and-Exchange-Site-Consolidations.aspx---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Ya /o=Labtest/ou=Labo/cn=Recipients/cn=Depart doesn't exist anymore. Is that the prob?

On Tue, 24-Nov-09 22:26:01 GMT, SAMATA wrote:>Ya ‘/o=Labtest/ou=Labo/cn=Recipients/cn=Depart’ doesn't exist anymore. Is that the prob? Yes, it is.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Yup.... the DC which was removed would have been the OAL server.Do this, ESM--> Recipients --> Offline Address list --> Right click--> properties---> Check if the OAL server is a valid one, change it --. Click ok...Now right click again ---> Rebuild OAB.Remember --> You should never rebuild the Recipient update service as you Rebuild OAB.Ratishwww.MSExchangeGuru.com

OK I checked in ESM on "OFFLINE ADRESS BOOK" folder. This is what I get: ------------------------------------------------------------------/o=Labtest/cn=addrlists/cn=oabs/cn=Default Offline Address List/ - OAB Version 2- OAB Version 3a- OAB Version 4 EX:/o=Labtest/ou=Labo/ - OAB Version 2------------------------------------------------------------------ cn:Depart and ou:Labo don't exist anymore. Labtest it the old domain, it just Lab now. I don't known if it's normal or not but I think the old domain Labtest is still remained after they update from Exchange 5.5 to Exchange 2003 Ok I just want to confirm: - Do I need to delete "EX:/o=Labtest/ou=Labo/" and just rebuild OAB?

On Wed, 25-Nov-09 15:01:59 GMT, SAMATA wrote:>>>OK I checked in ESM on "OFFLINE ADRESS BOOK" folder. This is what I get: >>------------------------------------------------------------------/o=Labtest/cn=addrlists/cn=oabs/cn=Default Offline Address List/ >>- OAB Version 2- OAB Version 3a- OAB Version 4 >>EX:/o=Labtest/ou=Labo/ >>- OAB Version 2------------------------------------------------------------------ >>cn:Depart and ou:Labo don't exist anymore. >t it the old domain, it just Lab now.Your problem has nothing to do with AD Domains. The legacyExchangeDNvalues are associated with Administrative Groups.>>I don't known if it's normal or not but I think the old domain Labtest is still remained after they update from Exchange 5.5 to Exchange 2003 >>Ok I just want to confirm: >>- Do I need to delete "EX:/o=Labtest/ou=Labo/" and just rebuild OAB? You need to (re)create the Administrative Group using the same name ithad before ("Labo") in the Exchange organization named "Labtest".Alternatively, you can create, say, a mail-enabled Contact and useADSIEDIT to change the legacyExchangeDN property value to"/o=Labtest/ou=Labo". I think that will satisfy the OABGen's need tohave a PDN for the other objects.You may yet have other problems with Free/Busy information if there'sno site folder store associated with the missing legacyExchangeDN --so recreating the AG and pointing the site folder server to a PF storeessary default site folders is probably a good idea.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

I think I start to understand now:1- The ORGANISATION NAME of Exchange 5.5 is still remained in Exchange 2003: You are right there is nothing to do with DC.2- So O=Labtest and ou= Labo are still there when I check in ESM: by the way, beside the globe it says "Laboratory Test", I think that is the new name of the Exchange 2003 organisation and "Labtest"should bethe old one in Exchange 5.53- If we are back to the previous warning:"The parent Legacy Exchange DN container value /o=Labtest/ou=Labo/cn=Recipients/cn=Depart was not found ""Depart" is it a mailbox? Is that mean it searches the mailbox?Thank you for your advices.

On Thu, 26-Nov-09 05:10:43 GMT, SAMATA wrote: Legacy Exchange DN container value ‘/o=Labtest/ou=Labo/cn=Recipients/cn=Depart’ was not found ""Depart" is it a mailbox? Is that mean it searches the mailbox?Thank you for your advices. If the Administrative Group is still present then it may be that therewas once a container in the 5.5 Exchange named "Depart" beneath the"Recipients" container.One way to see what AD objects have that as part of thierlegacyExchangeDN is to use csvde.exe to export information to a CSVfile.csvde -f depart.csv -d "dc=yourADdomain,dc=tld" -r"legacyexchangedn=/o=Labtest/ou=Labo/cn=Recipients/cn=Depart*" -llegacyexchangedn,displayname -p subtreeIf there are no items with the exact name"/o=Labtest/ou=Labo/cn=Recipients/cn=Depart", but there are items thathave values like /o=Labtest/ou=Labo/cn=Recipients/cn=Depart/cn=blahthen "/o=Labtest/ou=Labo/cn=Recipients/cn=Depart" is, indeed, themissing name.In my last post I said you could try creating a mail-enabled Contact the value of the legacyExchangeDN to"/o=Labtest/ou=Labo" -- but that was before you verified that therewas an AG with that name already in your AD. If you use"/o=Labtest/ou=Labo/cn=Recipients/cn=Depart" as the new value for thelegacyExchangeDN that might remedy your problem.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich,I ran the command csvde as you suggested and Ialso created a contact named "Depart" in "Labo". That contact show me when I checked by ADSI Edit: legacyExchangeDN"/o=Labtest/ou=Labo/cn=Recipients/cn=Depart".Of course I have many values like /o=Labtest/ou=Labo/cn=Recipients/cn=Depart/cn=blablabla...But the warning is still there: The parent Legacy Exchange DN container value /o=Labtest/ou=Labo/cn=Recipients/cn=Depart was not found ...Is there any thing elseI can do?

On Tue, 1-Dec-09 06:00:03 GMT, SAMATA wrote:.Is there any thing else I can do? Look here:http://blogs.msdn.com/dgoldman/archive/2005/11/18/494545.aspxAnd read this section: Situation #1: (Removed PDN Entry) When you received an event id 9341 during an OAB generation. Reading the entire post isn't a bad idea. :-) I left out the partabout the X500 address type. :-(---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich,The warning has disappeared now since a couple of days. I don't know if because I havecreated a contact with legacyExchangeDN="/o=Labtest/ou=Labo/cn=Recipients/cn=Depart" as you suggestedmake that warning disappeared after certain time.Anyway I just want to thank you especially for all your suggestions and also the others members for their help.