http://www.confusedamused.com/notebook/communicator-and-damaged-address-book-files/ Fri, 26 Feb 2010 17:26:04 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://www.confusedamused.com/notebook/communicator-and-damaged-address-book-files/comment-page-1/#comment-1326 The C Stands for Compact « Confused Amused Fri, 18 Dec 2009 16:06:36 +0000 http://www.confusedamused.com/?p=666#comment-1326 <p>[...] Communicator and Damaged Address Book Files [...]</p> [...] Communicator and Damaged Address Book Files [...]

]]> http://www.confusedamused.com/notebook/communicator-and-damaged-address-book-files/comment-page-1/#comment-1174 Constantino Tobio Mon, 30 Nov 2009 18:11:37 +0000 http://www.confusedamused.com/?p=666#comment-1174 <p>Ran into pretty much the same problem, with one additional wrinkle- all 2500 of our clients were on 3.5.6907.37 at about the same time as the absync.exe got upgraded to .37 as well. What we see is that even in deleting the galcontacts.db file in that case, it will get recreated just fine, but then just as soon will corrupt and not upgrade after applying the full. The fix for us was to write in our deployment scripts for SCCM a procedure to delete the user's galcontacts.db before applying the patch. Simply upgrading to 3.5.6907.56 with a broken galcontacts.db present was not enough.</p> Ran into pretty much the same problem, with one additional wrinkle- all 2500 of our clients were on 3.5.6907.37 at about the same time as the absync.exe got upgraded to .37 as well. What we see is that even in deleting the galcontacts.db file in that case, it will get recreated just fine, but then just as soon will corrupt and not upgrade after applying the full. The fix for us was to write in our deployment scripts for SCCM a procedure to delete the user’s galcontacts.db before applying the patch. Simply upgrading to 3.5.6907.56 with a broken galcontacts.db present was not enough.

]]>