• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 507
  • Last Modified:

Only few MOC encountered "Cannot Synchronize Address Book"

Strange! I do not why it sudden happen. It was working last week.
My machine is installed MOC 2007 to connect to OCS2007. It is connected but appear "Cannot Synchronize Address Book". Further check, only affected to Distribution Group. I search one of Distribution Group, it found then I add in my contact list. It appears on my contact list, but showing "Distribution Group service cannot be performed this action..."

I use my colleague computer and logon to my account. It is perfectly working well. I tried other machine also the same, it is working fine. Except my own machine cannot.

I uninstalled MOC2007, and reinstall it. It is the same.

Please advice.
0
chekfu
Asked:
chekfu
  • 2
  • 2
1 Solution
 
chekfuAuthor Commented:
Hi Experts
your reply is very much appreciated. I really have no idea.
0
 
NerdAtLarge403Commented:
Since everything is working fine on your colleagues machines with the same credentials the problem must be local to the machine which is failing.

Try looking in the %appdata%\Local\Microsoft\Communicator\ folder and empty it out.  In that folder you will find GalContacts.db is the local copy of the corporate address book that gets pulled down from the Address Book server to your Communicator client when you start it up.  If Communicator is for some reason unable to write data to this folder at startup (such as file rights issues, disk integrity problems, folder redirection via group policy problems, etc.) then I think the outcome would be similar to what you describe.

If this doesn't work next steps would be providing us with the full distribution group error message you are receiving plus any associated Events from your machine's event logs.  Would also be helpful to know if you are using either of Enterprise Voice or Remote Call Control, and if yes - which one?  

Finally, do some direct verification of your Address list service; Right click the pool name in question in the OCS management console, choose 'Properties' -> 'Web Component Properties'.  Go to the "Group Expansion" tab and take note of the internal and external URLs.  Verify that they are both functioning and accessible from the workstations in question by opening the URLs in a web browser (you should see something like the attached screenshot (ExpansionService.jpg)).

Is there anything else about the failing workstations that is distinct - for instance are they on a different network segment from the functioning ones?

Cheers.


ExpansionService.JPG
0
 
chekfuAuthor Commented:
Finally, it was because the permission was not set correctly on the folder where galcontacts found.

Thank you for all reply. Appreciated!
0
 
dahelpdeskCommented:
Are you saying it was the permissions to the user profile folder on the client machine, or the AddressBook folder on the server with all the lsabs and dabs files?
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now