Hi Florian,

We have Outlook 2010 with Exchange 2003. The issue we experienced did not affect searches, but it did result in a login dialog being presented to the user every 2 or 3 minutes, which they had to cancel. Supplying correct credentials did not clear the dialog. We likewise had to pull this update due to the effect on the end user.

Regards,

Ben

• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM
• Unproposed as answer by florian Winkelried Friday, March 13, 2015 12:27 PM

Same issue as Ben regarding login dialog (Outlook 2010 - Exchange on SBS2003). Removed update and problem goes away.

Regards,

Pete

• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM
• Unproposed as answer by florian Winkelried Friday, March 13, 2015 12:28 PM

Hi,

We have Outlook 2010 with Exchange 2010. After installing the latest Patches for Outlook (KB2956128) we had problems with the search. We couldn't search (Advances search) in shared calendar.
Error: Outlook cannot perform your search. Outlook cannot display this view.
After unistalling this patch the search works fine. Has someone the same problem with this patch?

Thanks

florian

• Edited by florian Winkelried Thursday, February 12, 2015 3:12 PM

Hi Florian,

We have Outlook 2010 with Exchange 2003. The issue we experienced did not affect searches, but it did result in a login dialog being presented to the user every 2 or 3 minutes, which they had to cancel. Supplying correct credentials did not clear the dialog. We likewise had to pull this update due to the effect on the end user.

Regards,

Ben

• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM

Exactly same problem as Florian, can no longer search shared calendar since KB2956128 update. Taken all morning to work it out by removing Office, reinstalling and applying the recent updates one by one. We have Outlook 2010 and Exchange 2013. Removed this one update and works again.

Edit: Slightly different error message actually:- "The attempted operation failed. An object could not be found". We use custom Outlook forms.

Oli

• Edited by Oli-A Thursday, February 12, 2015 1:50 PM
• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM
• Unproposed as answer by florian Winkelried Friday, March 13, 2015 12:28 PM

Same issue as Ben regarding login dialog (Outlook 2010 - Exchange on SBS2003). Removed update and problem goes away.

Regards,

Pete

• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM

Exactly same problem as Florian, can no longer search shared calendar since KB2956128 update. Taken all morning to work it out by removing Office, reinstalling and applying the recent updates one by one. We have Outlook 2010 and Exchange 2013. Removed this one update and works again.

Edit: Slightly different error message actually:- "The attempted operation failed. An object could not be found". We use custom Outlook forms.

Oli

• Edited by Oli-A Thursday, February 12, 2015 1:50 PM
• Proposed as answer by Justin Blocksom Thursday, February 12, 2015 2:55 PM

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 Thursday, February 12, 2015 2:26 PM

UPDATE: Search function appears to have restored now as well. Perhaps there was a file that needed to sync and/or rebuild? OCS is now fully functional on the two PCs after removing KB2956128 and giving it 15 to 30 min for search function to be restored on the PC with OCS running.

• Edited by Justin Blocksom Thursday, February 12, 2015 2:57 PM

Hi

We had also OCS 2007 R2 but no Problems with this. Only the search issue in OL2010. No Appcrash or something

We have Outlook 2010 and Exchange 2010.  After Install of this KB, we noticed that Disable Attachment Preview option doesn't work. Whether we check it or have it unchecked, attachment preview is still enabled.  

After uninstalling it, attachment preview was disabled.

Windows 7 Enterprise and Office 2010 Professional and attachments were completely disabled.  Preview didn't work and double clicking attachments would give operation failed and a message about no permissions to write file to temporary folder.  Removed KB2956128 and everything working again.

Win 2008R2, Exchange 2010, TMG2010

Clients Win7 with Office 2010

Internal clients with direct connection to Exchange (no cache mode) do not show problems right now.

External Laptop Clients (not domain joined) get Password prompt in Outlook and have to cancel the prompt each time.

Maybe a problem with autodiscover? Our autodiscover.xml is not reachable from outside the LAN at the moment but this was not a problem in the past.

After removing the patch, the password prompt problem went away.

Entering the domain credentials at the prompt didnt help. The prompt came up again and again but Outlook was still connected in the background to Exchange.

Will investigate and check the autodiscover problem next week.

Did the patch change anything concerning Outlook 2010 behaviour when connected in cached mode over RPC?

• Edited by justanicename 19 hours 55 minutes ago

Win 2008R2, Exchange 2010, TMG2010

Clients Win7 with Office 2010

Internal clients with direct connection to Exchange (no cache mode) do not show problems right now.

External Laptop Clients (not domain joined) get Password prompt in Outlook and have to cancel the prompt each time.

Maybe a problem with autodiscover? Our autodiscover.xml is not reachable from outside the LAN at the moment but this was not a problem in the past.

After removing the patch, the password prompt problem went away.

Entering the domain credentials at the prompt didnt help. The prompt came up again and again but Outlook was still connected in the background to Exchange.

Will investigate and check the autodiscover problem next week.

Did the patch change anything concerning Outlook 2010 behaviour when connected in cached mode over RPC?

• Edited by justanicename Friday, February 13, 2015 3:58 PM

Update 2015/02/18

We fixed our autodiscover problem. 

After the external standalone (not domainjoined) Laptops (using RPC over HTTP) were able to get the autodiscover.xml file from the Exchange Server, the password prompt disappeared.

So our problem was fixed by getting autodiscover to work, even if autodiscover was not needed before and everything worked fine without autodiscover. Seems KB2956128 changed something on the Outlook Client that forced him to try to connect to autodiscover. The password prompt came up because autodiscover tried to connect to the Exchangeserver and pull the xml file bute the Authentication Delegation on the TMG was not correct and the client was not able to connect to this virtual directory, so the login came up again and again.

So for everyone with the same problem:

-Check if autodiscover works from internal and external network and also check if the virtual directories on your Exchange are all ok because the client also tries to connect to ews and oab and certificates and A Records in the DNS have to match or you might run in the next problem with a certificate missmatch error.

HTH

• Edited by justanicename Wednesday, February 18, 2015 1:33 PM

Update 2015/02/18

We fixed our autodiscover problem. 

After the external standalone (not domainjoined) Laptops (using RPC over HTTP) were able to get the autodiscover.xml file from the Exchange Server, the password prompt disappeared.

So our problem was fixed by getting autodiscover to work, even if autodiscover was not needed before and everything worked fine without autodiscover. Seems KB2956128 changed something on the Outlook Client that forced him to try to connect to autodiscover. The password prompt came up because autodiscover tried to connect to the Exchangeserver and pull the xml file bute the Authentication Delegation on the TMG was not correct and the client was not able to connect to this virtual directory, so the login came up again and again.

So for everyone with the same problem:

-Check if autodiscover works from internal and external network and also check if the virtual directories on your Exchange are all ok because the client also tries to connect to ews and oab and certificates and A Records in the DNS have to match or you might run in the next problem with a certificate missmatch error.

HTH

• Edited by justanicename Wednesday, February 18, 2015 1:33 PM
• Proposed as answer by Thomas Stensitzki (MCM, MCSM) Tuesday, April 21, 2015 9:36 AM
• Unproposed as answer by florian Winkelried Tuesday, April 21, 2015 10:21 AM

Hi

I have found problems with KB2956128 in our environment with Windows 7 64bit, Outlook2010 DK / Exchange 2003.

Outlook 2010 crashes intermittently when you create a meeting with participants from your private contactlist and then go into ScheduledView.

If I uninstall KB2956128 on the clients, everything Works fine Again.

After KB2956128 was installed I had an issue with a Security Alert popping up every 2-3 minutes in Outlook.  This is in an environment where the server is running Exchange 2003 (SBS 2003) and the clients are running Outlook 2010 (Office 2010).

I uninstalled KB2956128 and then did a check for updates and then I hid the update on all of the computers.  Yesterday I got a call from the client to inform me that the users are getting the Security Alert in Outlook agian.  I checked the computers and sure enough the KB2956128 was listed as being installed on the client computers.

The weird thing is when I go to the list of hidden updates there are no updates listed (I am certain that I hid the update after I uninstalled it) and when I go to Programs and Features to uninstlall KB2956128 it doesn't show up in the list.

Now I'm stumped because I no longer have an option to uninstall KB2956128 and it is causing the Security Alert to pop up in Outlook every 2-3 minutes, which I'm sure the users aren't going to want to live with for the next 4 months until the server is upgraded.

Has anyone else run into this issue where KB2956128 is reinstalling itself after you uninstalled it?

Yes. KB2956128, KB2956203 and now KB2965295 are all bad news for our Outlook Communicator 2007 R2 environment. ALL crash OCS 2007 R2 every few min. (see the above error in the thread for the crash message)
I am hearing it may have something to do with the Exchange 2013 backend we are running but nothing concrete on that. The common denominators appear to be: Installed = Outlook 2010 x32 (x64 appears to be unaffected), OCS 2007 R2, and Exchange 2013 backend it crashes OCS every few min.  For us, we now test all Outlook patches very carefully during the week following a patch Tuesday as this has been a very bad few months of releases from Microsoft and we are thus not installing these three patches in our Enterprise.

I recently started receiving reports of this error as well when users search shared contacts. Haven't tested yet but appears KB2965295 was suppose to resolve the issue but has already been superseded by KB3015585 which should also resolve the issues as well. I'll probably test this weekend.

We checked patch KB3015585 also and this will resolve our issues with the advanced search in Outlook.

Now it works fine.

• Marked as answer by florian Winkelried Saturday, May 16, 2015 4:18 PM