OCS Client Error RRS feed

  • Question

  • All of our clients are reporting this error:

    Communicator cannot synchronize with the corporate address book because the corporate address book file appears to be damaged. Contact your system administrator with this information.

    Any ideas? Nothing has changed in our environment, it just showed up one day!
    Monday, September 21, 2009 10:08 PM

All replies

  • It's possible for the local cached copy of the Address Book to be corrupted.  Simply delete the file(s) and restart Office Communicator.  A new copy should be downloaded automatically.

    For OC 2007

    %userprofile%\Local Settings\Application Data\Local\Microsoft\Communicator\galcontacts.db

    For OC 2007 R2

    %userprofile%\Local Settings\Application Data\Local\Microsoft\Communicator\sip_user@domain.com\galcontacts.db

    Delete both the .db and .db.idx files
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, September 21, 2009 10:40 PM
  • We are getting this same error on 3 users (out of 300). We can close out of Outlook 2007 and Communicator R2 and run fixmapi.exe from the command line and that fixes it for a few hours.

    This is a new OCS 2007 R2 setup.

    Could it be AV that is scanning the .db file and corrupting it? We use SEP.

    Tuesday, October 6, 2009 2:12 PM
  • Same issue here. The last date modified for GalContacts.db is just over 7 days ago when the error "Cannot synchronize" triggers.

    Deleting the local cache is easy, but not an appropriate solution for hundres / thousands of seats, unless it's somehow automated.

    In any case deleting it doesn't address the root cause.

    Does anyone have other thoughts on this issue?

    Wednesday, October 14, 2009 8:08 AM
  • same issue here. brand new ocs2007 r2 install. appears only on machines with ol2007. very strange.
    best regards,
    Wednesday, October 14, 2009 2:38 PM
  • We have seen this issue before. As for the cause, it ranges from installing the CWA components on the FE to incorrecct authentication settings. The most common cause however has to do with "trusted sites" under I.E. Make sure your OCS FE server is in that list and that normally resolves the issue.

    If you continue to struggle, uninstall the web components from the OCS FE server and reinstall. That should resolve issue.

    Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa
    • Proposed as answer by Andrii Veselov Friday, October 16, 2009 9:18 AM
    Thursday, October 15, 2009 6:18 AM
  • OK here's a new twist to the seemingly never-ending Address Book issue saga. The October 2009 (CU3) update introduced changed delta update behaviour and a new registry key

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator\GalUseCompactDeltaFile (Type: DWORD)

    0: Do not use the address book delta file.
    1: Use the address book delta file (default).

    that can be used to determine the client behaviour how to download the address book file. Even after forcing the download with 0 delay using the above mentioned KB 972403, we still ended up with random Address Book sync issues (corrupt etc.).

    Now we are setting the GalUseCompactDeltaFile registry to 0 to force it not to mock around with deltas anymore (cause it ain't working).

    Hopefully this will fix it once and for all. And please, Microsoft, can you document in your CU release notes what behaviour changes you are making ... still quite big gaps here.

    Friday, December 18, 2009 2:40 PM