SharePoint 2010 - Search service is not able to connect to Administration component server
Hey folks!
In this blog post, I would write about most generic issue in SharePoint 2010 search service application and I am sure many of you have already come across this:
In SharePoint 2010 - When you try to browse to a Search Service Application (SSA), it shows he below error:
"System Status:
Crawl: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component c8519b74 status -<GUID> in search application Search Service Application is in a good state and try again."
Additionally, you should see below errors in the Event logs:
"Description: The Execute method of job definition Microsoft.Office.Server.Search.Administration.CrawlReportJobDefinition (ID 6dd22d5b-45cb-4860-aa01-d7f7d227a2f6) threw an exception. More information is included below.
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '9eff6ca0-1e01-4bf4-9653-b26ea54d0e5f' in search application 'SP2010 - Search Service Application' is in a good state and try again. "
If you run PowerShell command 'Get-SPEnterpriseSearchServiceInstance', it will show "{}" (NULL) in AdminComponents field.
To get rid of this, follow below steps:
Browse SSA through CA and see which server is hosting Administration component, UI should look like below:
So with above example SP2010NEW is the server that is hosting Search Administration component. Login to that server.
Run below PowerShell command:
$varInstance = Get-SPEnterpriseSearchServiceInstance -local (Assuming that you have only one SSA in farm)
If you type $varInstance and hit Enter key, you should see SharePoint Server Search instance details.
If you see it disabled then run another PS command -----> Start-SPEnterpriseSearchServiceInstance -Identity <servername>
Once above runs successfully, execute below:
$varSearchApp = get-spenterprisesearchserviceapplication
Now set search Admin component:
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance
After it gets completed successfully, you need to wait for sometime, may be about 5-10 minutes. Admin component should be ready and you should be able to browse SSA.
Feel free to raise your questions. :)
Comments
Anonymous
January 01, 2003
OK. Tried your trick but nothing occured on the server. Still has the one error on the top of the screen for the search Service Application. I suspect that there is an issue with the service accounts that the Foundation Search service or the Search V14 service is using. Not sure what should match the account the the app pool runs in and which should match the remaining service accounts on the Sharepoint services.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
In my case, this error started happening after I installed the latest CUs. After looking for many different alternatives, I found the following article that solved my problem, technet.microsoft.com/.../hh285624.aspx. 1- Run the FAST Search Server 2010 for SharePoint shell as an administrator (Right click Microsoft FAST Search Server 2010 for SharePoint shell and select Run as administrator.) 2- Browse to <FASTSearchFolder>installerscripts, where <FASTSearchFolder> is the path of the folder where you have installed FAST Search Server 2010 for SharePoint, for example C:FASTSearch. 3- Type the following command to run the post-setup configuration script in patch mode: .psconfig.ps1 –action p 4- Verify that the FAST Search for SharePoint service has started.Anonymous
January 01, 2003
Very good, this tip worked fine in sharepoint 2013 at my environment! Thanks very much!Anonymous
January 01, 2003
Thanks, "Start-SPEnterpriseSearchServiceInstance -Identity " made it work :)Anonymous
January 01, 2003
Wow, thanks a lot!! Been looking for this solution for some time, now, your instructions helped me out Big Time!!Anonymous
December 01, 2011
The comment has been removedAnonymous
January 08, 2012
Hi Pooja, Thanks very much for your solution, worked a treat!! :-))))Anonymous
May 22, 2012
The comment has been removedAnonymous
June 07, 2012
When I browse to SSA through CA, the topology section never resolves. The server that originally managed search administration has left the farm. While I tried to remove it gracefully, it appears that did not happen. How can I recover / create a Search Admin on an existing farm?Anonymous
June 19, 2012
So... What if you done all the above steps, but nothing changed after the last command? Do I need to restart the server? Can I run some checks to see if I did anything wrong in the above process? Can yAnonymous
June 19, 2012
Did all of the above, but in CA the error when clicking on the Content SSA still remains. Anyone found out why this happens? Makes it alot easier to understand the cause and to avoid. Does this error implicate any missed out steps in the initial installation process?Anonymous
July 19, 2012
I faced same issue and in my case i simply restarted search service and timer service and it fixed the issueAnonymous
July 23, 2012
Hi Thanks, had some trouble and no time to restart the server. This is a great postAnonymous
September 12, 2012
The comment has been removedAnonymous
September 13, 2012
I have been struggling with this for 2 days now and came across your solution which worked a dream for me. I had tried many other things but this was the perfect solution. Very many thanks.Anonymous
October 04, 2012
Thank!!! this solve my problem, after a "disaster recovery Scenario" the search service get into this state.Anonymous
October 15, 2012
Great post! Very easy to understand. Thanks for posting on this.Anonymous
December 04, 2012
Out of curiosity, how should we be seeing the SSA through CA if the site isn't available in the first place?Anonymous
July 02, 2013
The comment has been removedAnonymous
October 17, 2013
The comment has been removedAnonymous
December 17, 2013
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance this helped me to get rid of The search service is not able to connect to the machine that hosts the administration c.....Thanks a ton....Anonymous
January 14, 2014
The comment has been removedAnonymous
March 19, 2014
Great - Thanks