SharePoint 2010 - Search service is not able to connect to Administration component server

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.

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"Sorry, Word Web App can't open this ... document because the service is busy." Office WebApp

Problem: Intermitten requests are not returning the pdf/word documents.  Most requests are working and occasionally 1 request doesn't work.  Every 4th request tries to get the pdf to display on Office Web Apps for a few minutes without any error message and then stops trying and displays the message "Sorry, Word Web App can't open this ... document because the service is busy." Initial Hypothesis: Originally I thought it was only happening to pdfs but it is happening to word and pdf documents (I don't have excel docs in my system).  My monitoring software SolarWinds is badly configured on my OWA servers as the monitor is showing green, drining into the servers monitoring the 2 application monitors are failing.  The server should go amber if either of the 2 applications fail and in turn red after 5 minutes.  At this point I notice that I can't log onto my 4 OWA/WCA server.  Web request are not being returned.  I look at my KEMP load balancer and it says al
Continue Read

Unable to create a "Send to Connection"- verification failed -url is a not a valid routing destination

ISSUE : Unable to successfully create a send to connection. When creating the Send to connection from Sharepoint 2010 Central Administration and click on Test URL for the Destination URL , we get the following error "verification failed -url is a not a valid routing destination" we see the following entry in the ULS logs Url validation failed for http://gmallya.test.com/sites/testrecordcenter/_vti_bin/OfficialFile.asmx   during Record and document center connection configuration with exception The request failed with HTTP status 401: Unauthorized .:  at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)     at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)     at Microsoft.SharePoint.OfficialFileSoap.GetServerInfo()     at Microsoft.SharePoint.ApplicationPages.OfficialFileAdminPage.<>c__DisplayClass2.&l
Continue Read