Forum Discussion
Search Issue After Installing KB4461549 (Dec 2018 CU)
My question: What is the best way to get support for this? SP2013 has moved out of mainstream support, and so I am not quite sure the right way to report this issue other than paying $500 to open a ticket.
Background: We installed the patches for December 2018 as while most of our search web parts still seem to work fine, there is one that crashes with the message "Sorry, something went wrong" with the network trace showing a call to the Client.svc ProcessQuery endpoint. It only crashes when the user is still anonymous. Once they login they do not get the error - and it is really only on this one page. The other pages will load their search results web parts without issue.
I created a test page to reproduce the error: https://www.wecc.org/Lists/WECCMeetings/DispForm2.aspx?ID=14031 - note we do geoblock so I apologize to those outside the U.S. that might have trouble accessing our site. Also note, I have a workaround in place that uses the Search REST API to replace the crashed query on the main DispForm.aspx (remove the 2) with the proper results.
Notes: KB4461549 - https://support.microsoft.com/en-us/help/4461549/Security-Update-for-SharePoint-Enterprise-Server-2013-December-11-2018
More detailed information available on the TechNet post I also created: https://social.technet.microsoft.com/Forums/en-US/ac9a250b-8739-42a4-b457-347893765b2f/clientsvc-processquery-fails-with-invalid-url-argument?forum=sharepointsearch
It looks like there has been some more activity on this, with https://support.microsoft.com/en-us/help/4052414 being published, that documents how to revert back to the old (potentially insecure) behavior. On your server, open a PowerShell prompt and run the following code:
$web = Get-SPWeb https://server/path/to/web $web.AllProperties.Add("SyncSearchAllowed", 1) $web.Update()Boom. The web parts start working again with the same behaviors that existed prior to the December 2013 security patches. I would assume it re-opens the information disclosure vulnerability, so certainly be aware of the risks before proceeding.
1 Reply
It looks like there has been some more activity on this, with https://support.microsoft.com/en-us/help/4052414 being published, that documents how to revert back to the old (potentially insecure) behavior. On your server, open a PowerShell prompt and run the following code:
$web = Get-SPWeb https://server/path/to/web $web.AllProperties.Add("SyncSearchAllowed", 1) $web.Update()Boom. The web parts start working again with the same behaviors that existed prior to the December 2013 security patches. I would assume it re-opens the information disclosure vulnerability, so certainly be aware of the risks before proceeding.