Answered by:
Update KB2850058 breaks search

Question
-
I find myself in a position again around a recent SharePoint update. I installed KB2850058 on a single server farm (test environment, not making the windows update mistake ever again with SharePoint 2013) that did not have a previous install of one SharePoint update (KB2837628) but was otherwise up to date patch wise. I installed this updated first, before doing any of the other patch Tuesday updates, and immediately after install I cannot create a search web part (common language runtime error on creation), and I cannot create a search center page (unexpected error occurs). My thought here is that this is a CU including KB2837628 (which I create a previous topic on as it did the exact same thing) but as per usual, none of this information is mentioned on the Microsoft page, or on the security bulletin the update page links to. BE CAREFUL WITH THESE UPDATES.
- Edited by Theantioch Tuesday, January 7, 2014 9:07 PM
Wednesday, December 11, 2013 6:22 PM
Answers
-
This update for SharePoint Foundation 2013 should fix the issue:
http://support.microsoft.com/kb/2760625
Lucian Baciu
- Proposed as answer by Steven Van de Craen Thursday, March 20, 2014 7:00 PM
- Marked as answer by Theantioch Thursday, March 20, 2014 7:30 PM
Thursday, March 20, 2014 6:06 PM
All replies
-
Doing a bit of additional reading on this,
here: http://technet.microsoft.com/en-us/security/bulletin/ms13-100
I'm using SharePoint 2013 foundation, and on this page this is listed as non-affected by the security fix. My theory here is that this is the issue, and windows update isn't detecting that what's actually installed is SharePoint foundation instead of enterprise. I don't know of any way to go about testing this however, but if anyone wants to try this on an enterprise install then on foundation and report the results back I would be appreciative.
- Edited by Theantioch Wednesday, December 11, 2013 6:40 PM
Wednesday, December 11, 2013 6:38 PM -
I've opened a support case with Microsoft on this issue. I'll post updates to my post (http://www.sharepointblogs.be/blogs/vandest/archive/2013/12/10/sharepoint-foundation-2013-broken-search-experience.aspx) but also try to post them here.Thursday, December 12, 2013 3:08 PM
-
Thanks for the reply on this. I saw your blog post previously about the issue, seems to be the only solid info on this problem that I have seen.
- Edited by Theantioch Thursday, December 12, 2013 5:01 PM
Thursday, December 12, 2013 4:56 PM -
No problem. It bothers me though that I can't seem to repro this issue myself. If anyone has reproducible steps please share them. I can't get that KB to install onto my system. There must be some combination of patches that DOES allow it to install, but I'm having hell finding it.Friday, December 13, 2013 8:57 PM
-
Its tough for me to provide repro steps beyond, install patch, watch chaos ensue as this SharePoint server had been up to date and receiving regular patches since June. To my knowledge, outside of one or 2 minor SharePoint patches (and all available windows patches) released between June and now its been operating as normal. You say it wont install in your environment, is it erroring out or just saying its not applicable?Friday, December 13, 2013 9:08 PM
-
I managed to reproduce the issue and confirm it is caused by KB2850058. I hope Microsoft PSS can pick this up quickly. See here: http://www.sharepointblogs.be/blogs/vandest/archive/2013/12/10/sharepoint-foundation-2013-broken-search-experience.aspx
Is this how it got installed on your env as well?
Saturday, December 14, 2013 6:31 AM -
Yup, single server installation of the English sku of sharepoint 2013 foundation. No other software installed on the server.Tuesday, December 17, 2013 10:17 PM
-
posting here with same problem so i can get an email when its fixed. no updates yet i can see on http://technet.microsoft.com/en-US/office/ee748587.aspx
the office 2013 update from jan 14th does not seem to directly address this issue so i have not deployed it. I would expect any sharepoint update would make that page above
Tuesday, January 28, 2014 5:01 PM -
A final word from the escalation engineer is that this will be fixed in the April 2014 Cumulative Update.
If you can't live without Search until that time you'll have to set up a new environment and avoid said hotfixes.
- Proposed as answer by Jason Warren Wednesday, February 5, 2014 9:42 PM
- Unproposed as answer by Theantioch Wednesday, February 5, 2014 11:31 PM
Wednesday, February 5, 2014 8:38 PM -
Thank you for your work on this Steven. While I believe we are close to a resolution I unproposed your response as the answer as the issue still has not been resolved. If/when the April CU comes out and it does prove to fix the issue ill be happy to mark it as such.
*Edit* I should say that I see that it was an moderator who marked this as the answer Steven, not you. I just wanted to state why I did not accept this as the answer.
- Edited by Theantioch Wednesday, February 5, 2014 11:42 PM
Wednesday, February 5, 2014 11:33 PM -
3 1/2 month update mark, Steven is still working with Microsoft towards a fix. Last we have heard from Microsoft is end of April, maybe, possibly. If your site is still broken DO NOT install SP1, this WILL NOT fix the issue and it will still break your search bar.Wednesday, March 5, 2014 5:29 PM
-
This update for SharePoint Foundation 2013 should fix the issue:
http://support.microsoft.com/kb/2760625
Lucian Baciu
- Proposed as answer by Steven Van de Craen Thursday, March 20, 2014 7:00 PM
- Marked as answer by Theantioch Thursday, March 20, 2014 7:30 PM
Thursday, March 20, 2014 6:06 PM -
Just installed, can confirm that search does appear to work. Will have to test all sites in the colllection.
Also even though the KB says "enterprise" i had no problem installing on foundation. I then rebooted the server and i think its fixed now.
Thursday, March 20, 2014 6:41 PM