We have a single Exchange 2007 SP1 server for our organization with all clients using Outlook 2007. We found that a couple recent hires have not shown in everyone's address book. At first we though it was related to cached vs. non-cached mode but it is not. Some symptoms I have found are: If I update the OAB, new files are created in C:\Microsoft Exchange Server\ExchangeOAB\cbb8f9d3...\ but not copied to C:\Microsoft Exchange Server\ClientAccess\OAB\cbb8f9d3...\ If I stop and start MSExchangeFDS, then 1) If ...\ClientAccess\OAB\cbb8f9d3...\ is empty then new files are created or 2) if ...\ClientAccess\OAB\cbb8f9d3...\ is NOT empty then new files NOT are created - i.e. the older one remain untouched. In either case, there are no errors in the event log and event 1008 shows as completed successfully to the proper Guid. As I said above, client problem is not related to cached mode. However, if I try to force an address book download on any client I get an 0x80190194, operation failed message. The directory, share and IIS permissions appear to be correct and our local Exchange consultant hasn't been able to determine the cause. Any troubleshoot ideas would be appreciated. Thanks, Jim

You say there are no errors in the event log, but just checking whether you ramped up diagnostics logging for the FDS service?Principal Consultant, Silversands | www.silversands.co.uk | www.msexchange.org/neil_hobson

I belive you are able to access new hire from OWA and non cached outlook mode. We see error 0x80190194 when using an Outlook 2007 client to download a Web Distribution enabled OAB and receive the following error (0x80190194) in Outlook when trying to download a Web Distribution only. This may be a reason for this error message is that when an Outlook 2007 client downloads the OAB files they are not being found on the Client Access Server. You can go your mailbox server (OAB Generation Server) and go to one of the following locations: Local directory - C:\Program Files\Microsoft\Exchange Server\ExchangeOAB Unc path - \\ExchangeServerName\OAB\<GUID of OAB> Copy the OAB directories that are needed for your clients over to the client access server location: c:\Program Files\Microsoft\Exchange Server\Client Access\OAB\ Once the files have been replicated to this directory the Outlook client will be able to download them and you will not receive this error. More Information:: http://social.technet.microsoft.com/Forums/en/exchangesvrdeploy/thread/079163a7-232a-4f93-9a16-aeef8b2a5c93 Anil

Hi, Can you try this: Force Update OAB Update-OfflineAddressBook “Name of Address Book” To update all OABs: Get-OfflineAddressBook | Update-OfflineAddressBookRegards from www.windowsadmin.info

Thanks for the responses. Neil, Even with the Eventloglevel high for both MSExchangeFDS\ General and Replication, I still see no errors, only information entries. Anil, there are files in ClientAccess\OAB\<Guid of OAB>. However, if they exist, new ones are not created when I stop then start MSExchangeFDS ManU PhiliP, doing and update either in the shell or in the console will recreate files in the - \\ExchangeServerName\OAB\<GUID of OAB> In reading the link http://social.technet.microsoft.com/Forums/en/exchangesvrdeploy/thread/079163a7-232a-4f93-9a16-aeef8b2a5c93 I see alphalapha1 referring to the OAB Application settings. Looking on our server I see no OAB specific AppPool. We have the following MSExchangexxxAppPool entries: OWA, Services, Sync, UM and Autodiscover . Should there be an entry for OAB? Jim

Hi, First, I would like to confirm the following questions: 1. Can you see the recent hires in Address Book when using OWA? 2. After copying the OAB file to Client Access\OAB\GUID folder, what do you mean that new one cannot be created? Does it mean that the new hire address cannot be added to Address List? If so, please let me know the detail error message when trying to add the new hire. Also, can you see the new hires in Address Book after copying OAB to CAS folder? Usually, there are two workarounds to resolve the OAB issue via following article: http://blogs.msdn.com/b/dgoldman/archive/2006/11/27/error-0x80190194-when-using-an-outlook-2007-client-to-download-a-web-distribution-enabled-oab.aspx Thanks.Novak Wu-MSFT

Novak, To answer number 1, yes I can see the new additions in the address book when using OWA. As for your question 2: A) If I update the Offline Address Book from within the Exchange Management Console, files will be updated in C:\Microsoft Exchange Server\ExchangeOAB\GUID\ but not in C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\ B) If I try the dgoldman work around 1 ( stop and start MSExchangeFDS) after doing A), above, then either; a) If the files exist already in the folder C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\ nothing happens to them. No new files or updated time stamps happen in the folder. Event 1008 does not error b) If I delete all the files in C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\ before I stop and start MSExchangeFDS, new files will be created in the folder. c) I can manually copy files into C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\ but... In any case, even with new files in C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\, clients still get the 0x80190194 Error. Thanks, Jim

please set Eventloglevel "expert" for both MSExchangeFDS\ General and Replication and restart the service, and post the warnings/error. The ExchangeOAB folder should be shared, in the Mailbox folder. Dhruv || Email - Polaris_1942@hotmail.com

After copying the new files to C:\Microsoft Exchange Server\ClientAccess\OAB\GUID\ folder, does the 0x80190194 error occur on each client or certain client when trying to download OAB? At this stage, I suggest you also refer to the following article to troubleshoot the issue. http://msexchangeteam.com/archive/2007/04/19/437902.aspx If the issue still occurs, please upload the Event log to the Skydrive ( www.skydrive.live.com ). Collect Event log ========================= a. Click "Start", input "eventvwr" (without quotation marks) in the Run command and press Enter. b. Right click on "Application" on the left frame, choose "Save Log file As"; in the pop-up window, click to choose the Desktop icon on the left frame, input "app" in the "File name" blank, and then click save. c. Right click on "System", with the same method, save it as "sys". d. Locate the two saved log files on the Desktop and upload them. Thanks.Novak Wu-MSFT