Wednesday, September 01, 2010

SharePoint 2010: Search Service is not able to connect to the machine that hosts the administration component

Had a strange Search error in a new SharePoint 2010 farm:

The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component 'bae8d161-c132-4570-aa0d-57baf6cf9d9b' in search application 'Search Service Application 1' is in a good state and try again."

I was unable to start any crawls as a result.

The search services were all started correctly but in the Application Services window it showed “Error”. The fix for me was to click on the Search Service Application name in the list of Application Services, choose Properties on the ribbon above, and change the Application Pool to another one (in my case, from SharePoint Web Services Default app pool to SharePoint Web Services System).

Hope it helps someone.

Posted by Nick Kellett at 2:02 pm Labels: , , , , ,

Actions:

11 comments:

  1. Andy4 October 2010 at 22:29

    That helped me out. Thanks for the Post.
    Do you know any reason why "SharePoint Web Services Default app pool" is not working for search service application.

    ReplyDelete
  2. Anonymous9 August 2011 at 14:40

    Thank you! That worked like a charm.

    ReplyDelete
  3. Smacker2 October 2011 at 03:22

    I had several issues with troubleshooting this particular error. What finally did the trick for me was to blast the cancerous search service app and configure one anew using central administration. Here is the how-to I used to repair my search service app woes.

    http://davidbajak.com/blog/post/2011/09/29/Fix-SharePoint-2010-Enterprise-Search-After-Using-AutoSPInstaller-Script-Installer.aspx

    ReplyDelete
  4. Smacker2 October 2011 at 03:29

    This comment has been removed by the author.

    ReplyDelete
  5. Anonymous10 October 2011 at 05:04

    The fix for me is the Reseting the Index in the search Administration page.

    ReplyDelete
  6. Zakir Chougle14 February 2012 at 05:19

    Thanks for the post. It helped me too.

    ReplyDelete
  7. alex12 June 2012 at 10:54

    yep. resetting the index for me too

    ReplyDelete
  8. Unknown7 December 2012 at 03:27

    Fix works great in SharePoint 2013 as well! Many hours later this was finally the answer!

    ReplyDelete
  9. Ismar Alikadic12 January 2013 at 01:47

    Thanks a million! This was my last resort after trying pretty much everything else except for rebuilding the farm.
    Any clues as to why Search errors out on the App Pool initially configured with?
    Thanks again.

    ReplyDelete
  10. Anonymous28 May 2014 at 08:48

    This is the fixed that worked in sharepoint 2013 after every fixed mentioned in the web failed

    ReplyDelete

Note: only a member of this blog may post a comment.

Subscribe to: Post Comments (Atom)