Export (0) Print
Expand All

Troubleshoot Communicator Synchronization Issues with the Corporate Address Book

Communications Server 2007 R2

You’ve just deployed Office Communications Server 2007 R2, and you have migrated a user account successfully or created a new account. You sign in for the first time and you see a red exclamation point on the Office Communicator icon in the notification area. Upon further investigation, you find that Communicator cannot sync the address book. What is going on here?

Author: Greg Anthony

Publication date: December 2009

Product version: Office Communicator 2007 R2

You’ve just deployed Office Communications Server 2007 R2 as part of your migration from Live Communications Server 2005 SP1 or Office Communications Server 2007, and you have migrated a user account successfully or created a new account. You sign in for the first time and you see a red exclamation point on the Office Communicator icon in the notification area as shown in Figure 1.

Figure 1. Red exclamation point

9ccf7da0-8f8d-410f-aad7-8d25ce90ff01

To get more information about this warning, open Communicator and click the View Missed Notifications folder. Cannot Synchronize Address Book, is displayed as shown in Figure 2.

Figure 2. Address Book sync error

a3a38066-5f8b-4946-b9c1-29e1f4188a49

When you click Cannot Synchronize Address Book to display details, Office Communicator presents the following message "Synchronizing with the corporate address book has not been configured by your system administrator. Contact your system administrator to configure this feature" as shown in Figure 3.

Figure 3. Corporate address book not configured

9e104a60-88bd-4e8a-8221-8dcbad213463

As a troubleshooting step, hold down the CTRL key and right-click the Communicator icon in the notification area. Click Configuration Information as shown in Figure 4.

Figure 4. Opening Communicator Configuration Information

57b8b171-9ded-4627-9b27-e9142eab2ba1

In the Office Communicator Configuration Information dialog box (Figure 5), verify that the URL provided by in-band provisioning, which is in the URL Internal From Server field, is the correct URL for your installation.

Figure 5. Verify URL Internal From Server

2f8a9fb9-7d43-49ce-aa18-399d81e48ab9

If the URL configured by in-band provisioning is correct, why is address book synchronization not configured? The reason is likely that Communicator defaults to high security mode for address book download. What the error means is that there is a Communicator policy entry for AbsInsideURL that specifies the address of the Global Address Book server to use when signing in, and it is not a secure URL that matches the https scheme. Administrators can specify a URL in the form of file://servername/addressbooksharename, but they must also configure the Communicator policy EnableSipHighSecurityMode to have a value of 2 or 0 to change Communicator’s behavior to allow download from non https URLs.

To verify the value of the EnableSipHighSecurityMode Communicator policy, check the registry on the local computer to see if the AbsInsideURL is set. If it is set, remove it, restart Communicator, and then test.

warningWarning:
Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.
To verify the value of the EnableSipHighSecurityMode Communicator policy
  1. Start Registry Editor (Regedit.exe).

  2. Find HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator.

  3. Right-click the registry name, ABSInsideURL, and then delete it.

  4. Exit Registry Editor.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft