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

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read