OL2010:Search Problems after install KB2956128

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


February 12th, 2015 8:31am

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

Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 9:50am

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

Regards,

Pete

February 12th, 2015 11:16am

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
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 1:48pm

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.





February 12th, 2015 2:22pm

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.
Free Windows Admin Tool Kit Click here and download it now
February 12th, 2015 2:57pm

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?



February 13th, 2015 3:57pm

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


Free Windows Admin Tool Kit Click here and download it now
February 18th, 2015 1:31pm

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

Now it works fine.

May 16th, 2015 12:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics