Archive

Archive for April, 2009

Communicator 2007 – cannot synchronize address book

April 1st, 2009 No comments

When this error is seen in the Communicator 2007 and Communicator 2007 R2 client, it can be a number of issues.

Here’s a few steps to check:

  1. Validate the password for the service account (RTCComponentService) used on the AppPool “LSGroupExpAppPool”
  2. Make sure the AppPool is started “LSGroupExpAppPool”
  3. Make sure the default website running the /Abs – application has a SSL certificate applied and that it’s responding on port 443 (https)
  4. Shut down and restart the Communicator 2007 (R2) client

These steps helped for me, when seeing the failure “Cannot synchronize address book” on all Communicator 2007 clients.

Address Book regeneration:

In case the Address Book needs to be regenerated, it can be done using these steps:

From the OCS folder: “C:\Program Files\Microsoft Office Communications Server 2007\Server\Core”:

  1. Run: “abserver –regenUR” and wait 5 min.
  2. Run: “abserver –SyncNow” and wait 5 min.

A few references:

Communicator 2007 and Outlook 2007 integration error

April 1st, 2009 1 comment

Error seen in Communicator 2007 R2:

There was a problem connecting to Microsoft office outlook. Your profile is not configured correctly. contact your system administrator with this information.

It can be solved in several ways:

  1. Make sure the default Outlook profile matches the “profile” = e-mail used for signing into OCS, equal your sip address:
    Go to: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
    Change DefaulProfile to your default profile name (Control Panel > Mail > Profiles)  

    Or go to: Control Panel > Mail > Profiles, select “prompt for a profile to be used”, restart outlook, select the profile, and click options, and select default profile. Restart outlook.

Another solution can be to run fixmapi.exe on the computer having this problem, If the default profile is already set correctly.

This solved the problem for me on a client running Vista and Outlook 2007 and no Exchange Admin tools.

Further reference: