Answered by:
New OC client cannot synchronize address book

Question
-
Currently we upgraded our OC clients from version 3.5.6907.22 to 3.5.6907.37. Then we found an issue that if using 3.5.6907.37 OC client, the client cannot get the latest address book info, but no issue on 3.5.6907.22 OC client.
Even we can see that if plan upgrade from .22 to .37, the GALcontact.db is there, but it is outdated.
We tried to delete the Galcontacts.db on the client workstation, reboot the workstation, and re-login to the OC client, then in the "%userprofile%\Local Settings\application data\microsoft\communicator\" I can only see there is a file "EndpointConfiguration.cache" is created.
BTW, we use the CWA and the address book is up-to-date.
Regards,
Timothy LauTuesday, August 18, 2009 3:58 AM
Answers
-
Ok thanks Gavin,
I finally found the support from other section in this forum. But this is really strange that if we dont make any changes to the regkey, what kind of default value it is.
Regards,
Timothy- Marked as answer by Gavin-ZhangModerator Friday, August 28, 2009 8:19 AM
Monday, August 24, 2009 9:43 AM
All replies
-
Monday, August 24, 2009 9:30 AMModerator
-
Ok thanks Gavin,
I finally found the support from other section in this forum. But this is really strange that if we dont make any changes to the regkey, what kind of default value it is.
Regards,
Timothy- Marked as answer by Gavin-ZhangModerator Friday, August 28, 2009 8:19 AM
Monday, August 24, 2009 9:43 AM -
hi
Please refer to http://support.microsoft.com/kb/972403/
Hope this helpful.
Regards!
According to the "Description of the Update for Communicator 2007 R2: July 2009" found here: http://support.microsoft.com/kb/969695/ The network issues described in http://support.microsoft.com/kb/972403/ are fixed in QFE2(.37). So how is this going to help with the issue of .37 not syncronizing the Address book.Tuesday, September 8, 2009 8:36 PM -
hi ssowa
Sure, you are ritht. it is my fault.
Thank you!
With my best regards!Thursday, September 10, 2009 2:43 AMModerator