17 Nov When you try to use Microsoft Office Communicator , you may receive the following error message: "Communicator cannot synchronize with the corporate address book. Please contact your system administrator." Additionally, when you try to locate a contact by searching in Communicator, the contact. 24 Apr When you log on to Microsoft Office Communicator, you receive the following error message: Cannot Synchronize Address Book. When you click the message to display the details, you receive the following error message: Cannot synchronize with the corporate address book. The cause of the problem is. 7 Jan When you use Microsoft Office Communicator to log on to Microsoft Office Communications Server, you cannot synchronize the corporate address book. When this occurs, you may experience the following issues: You may be asked for credentials for the corporate address book. Additionally, you may.
Close and reopen Communicator; this should force a hit against the ABS to pull down the full address book file. Use and inspect C:\Program Files \Microsoft Office Communications Server \Server\Core> - validateDB C:\Program Files\Microsoft Office Communications Server. 29 Nov Hello Experts - We have a new installation of Communications Server Standard all clients receive this error when connected. Although there is no problem in communication the popup is annoying. 3 Jul When I opened Communicator I received a "Cannot Synchronize Address Book" message with additional detail of "Cannot synchronize with the corporate address book. The cause of the problem is unknown. Please contact your system administrator with this information." I had this issue occur internally, i.e.
1 Apr When this error is seen in the Communicator and Communicator R2 client, it can be a number of issues. Here's a few steps to check: Validate the password for the service account (RTCComponentService) used on the AppPool “LSGroupExpAppPool”; Make sure the AppPool is started. 20 Jan Force the Communicator R2 Address Book to instantly update on both x86 and x64 machines. So let's say we take the registry key for our Communicator x86 (Communicator x64 not available) and run it on an x86 system. [ HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator]. This may be because the proxy server setting in your web browser does not allow access to the address book. I also checked settings listed in this article but did not see a problem: We have an OCS R2 server in place running on Server Enterprise.