Hey everyone, We've had our Exchange 2010 running in production for well over a year, but for some reason and without any configuration changes, the OAB has stopped displaying new and updated items in the GAL on Outlook clients (Cached Exchange mode is enabled). When I query the GAL from OWA, its updated correctly, but our clients are not. Also, when I navigate to C:\Users\<username>\AppData\Local\Microsoft\Outlook\Offline Address Books and delete the .OAB files on client machines, restart Outlook, and everything is there an updated. But if I then go and download a copy of the GAL from File -> Info ->Account Settings it reverts back to the previous GAL with incorrect/old information. Any ideas? I'm also getting the following error when manually updating the OAB through EMC or EMS: -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Action 'Update' could not be performed on object 'Default Offline Address Book'. Default Offline Address Book Failed Error: Failed to generate the content of the offline address book '\Default Offline Address Book'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform this operation. Error message : 'Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from RpcEpResolveBinding'. Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from RpcEpResolveBinding -------------------------------------------------------- OK -------------------------------------------------------

Hi, have you checked the status of the Exchange System Attendant Service? Is it running ans the starttype is automatic? regards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

In order to generate the OAB you need to have the following: 1. You need to have the correct permissions to the system attendant mailbox on the generation server. It is very possible that you have an active directory replication latency (if you have multiple domain controllers). 2. Starting this service fixed the issue, and I could now update the Address Book again.But rebooting the server, caused the service to not start again, so change it to delayed start and set the first and 2nd failure to restart the service and change restart the service after to 5 minutes. 3. If this is Exchange 2010 and you are using powershell, powershell will make remote calls to the powershell service on the exchange server. If your system attendant is not started, this will be a problem. Exchange will run with the system attendant service stopped. Thanks

Hi Der Hai, Please install the latest hotfix for the Exchange 2010 server and then try again to update OAB file. If the issue continues, please try the steps below: Increase the event log level Set-EventLogLevel identity "MSExchangeSA\OAL generator" -Level Expert;Create a new OAB file;Restart the System Attendant service, information store service and the File Distribution service;Try again to update the newly created OAB file to see what error message is recorded in application event log. If there is, copy the event ID and the error message. Let me know if there is anything unclear. Fiona Liao TechNet Community Support

Hi, Is there any update? Just for your reference: http://technet.microsoft.com/en-us/library/ff637981.aspx Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com Fiona Liao TechNet Community Support

Hi, could we help you? if your question is answered it would be great if you mark it accordingly because this may help others who have got the same or a similar question. Thanks a lot in advance Kind regards Thomasregards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Although the System Attendent service was running on my Exchange servers, after I set logging to Expert, I saw some other errors appear so I went ahead and restarted the System Attendent and the File Distribution service. After that I was able to update the OAB without any errors. Thanks everyone!