Tuesday 4 February 2014

Getting results failed: Microsoft.Office.Server.Search.Query.InternalQueryErrorException: Search has encountered a problem that prevents results from being returned. if the issue persists, please contact your administrator.

 
While running a Search on the Search Center as well Local search , on one of the Development farm got this error in SharePoint 2013 Search Center site
 
Getting results failed: Microsoft.Office.Server.Search.Query.InternalQueryErrorException: Search has encountered a problem that prevents results from being returned.  if the issue persists, please contact your administrator.   
 
Performed the following steps to resolve this after looking into ULS logs to identify the issue. Found that the search proxy was too busy to respond.
 
Get the Search Service Application ID

Get-SPServiceApplication
 
Get the Search Service Proxy ID

Get-SPServiceApplicationProxy
Remove the Search Proxy, replace SearchProxyID with the Search Service Proxy ID
 
 
Remove-SPEnterpriseSearchServiceApplicationProxy -Identity <SearchProxyID>
Replace the SearchID

$enterprisesearch = Get-SPEnterpriseSearchServiceApplication <SearchID>
$enterprisesearchproxy = New-SPEnterpriseSearchServiceApplicationProxy  -name SearchServiceProxy -Uri $enterprisesearch.uri.absoluteURI

$enterprisesearchproxy

IISreset

Reset the Indexer not required but did that anyways

Run a full crawl of the content sources

Boom issue resolved. This took some digging in the ULS to understand the exact issue and find the resoulution
Posted by at

13 comments:

  1. Anonymous19 March 2014 at 06:45

    the PS command before iisreset seems to be incomplete.

    ReplyDelete
  2. Anonymous27 August 2014 at 15:04

    Great work. save me so much time as I though about remove and redo all SSA.

    Thanks

    ReplyDelete
  3. Anonymous4 August 2015 at 04:21

    Same error here. Crawl seems fine, but error: Getting results failed.
    Above solution doesn't solve it.

    ReplyDelete
  4. Anonymous4 November 2015 at 01:17

    AWESOME!!

    ReplyDelete
  5. Andreas28 October 2016 at 01:27

    This comment has been removed by the author.

    ReplyDelete
  6. Unknown8 November 2016 at 05:14

    Did all of this and still ended up where I started. :(

    ReplyDelete
  7. Nate2 May 2017 at 13:09

    This worked great for me. I did have to run the SP Powershell Console as Admin to complete.

    Cheers

    ReplyDelete
  8. Unknown8 July 2017 at 07:28

    Hello! Thank you for providing this information! I like your blog and think it's very useful if you want to know all the news about microsoft dynamics software.
    Click for more here dynamics ax

    ReplyDelete
  9. Anonymous22 August 2017 at 07:58

    Hi,
    where to perform these operations:
    Get the Search Service Application ID

    Get-SPServiceApplication

    Get the Search Service Proxy ID
    .....
    so on

    ReplyDelete
  10. Blogger25 November 2017 at 14:36

    This comment has been removed by a blog administrator.

    ReplyDelete
  11. Rolwey10 September 2018 at 03:49

    I had this issue and resolved it by simply restarting the SharePoint Search Host Controller service on the SharePoint server.

    ReplyDelete
  12. Anonymous30 January 2019 at 10:43

    Restarting Search host contoller and search service resolved for me

    ReplyDelete

Subscribe to: Post Comments (Atom)