So glad I found this. A couple PC's in our environment that are setup to test the latest updates had OCS crash every 2 or 3 min after installing updates from the February patch release. Both PCs are running Office 2010 x32 with OCS 2007 R2.
Here is the crash message:
Problem signature:
Problem Event Name: APPCRASH
Application Name:
communicator.exe
Application Version:
3.5.6907.268
Application Timestamp: 5165ca9aFault
Module Name: MSVCR90.dll
Fault Module Version: 9.0.30729.6161
Fault Module Timestamp: 4dace5b9
Exception Code:
c0000005Exception
Offset: 0003b4a8OS
Version: 6.1.7601.2.1.0.256.48Locale
ID:
1033
Additional information about the problem:LCID:
1033
Was able to at least control the crashes using this tip I found here:
OCS client crash fix
"Method one: Configure PIM to sync with None or Windows Address Book
Office Communicator does not crash if you set the PIM to sync with None or Windows Address Book. However, Communicator operates with limited Outlook Integration.
1. Start Office Communicator.
2. On the green button menu, click Options, and then click Personal.
3. In the Personal information manager list, click either None or Windows Address Book."
Unfortunately, my search function was still broken. Began to dig around on this and while I found no Office Communicator patches released and installed from the February patch Tuesday, I found it odd that KB2956128 was actually listed as
being installed twice on both affected machines.
After I removed both instances of KB2956128 and set the OCS Personal Information Manager back to "Microsoft Office Outlook (Contacts, ...." it has been running without any crash for 30 min now.
HOWEVER, I still don't have the search function in OCS after having removed KB2956128, but glad it is not crashing every 2 min.
-
Edited by
Justin Blocksom
21 hours 26 minutes ago