This fix may apply to you if you have successfully completed an installation of SharePoint 2010 on your system but you are having trouble configuring /accessing the Search Service Application through the SharePoint Central Administration site. You may see the error message "The search service is not able to connect to the machine that hosts the administration component" and/or ask you to verify the administration component {GUID} is in a good state.
You may notice your Search Administration page refuses to load to completion and several links in the search sidebar also error when clicked.

Those who chose to script their installation of SharePoint 2010 using AutoSPInstaller may have noticed installation errors during the provisioning of Enterprise Search:

AutoSPInstaller Errors:
--------------------------------------------------------------
Set-SPEnterpriseSearchServiceApplication :
The search service is not able to connect to the machine that hosts the administration component.
Verify that the administration component '93c10c63-1bf5-45a8-90ae-a2f48e22f440' in search application 'Search Service Application' is in a good state and try again.
At C:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2608 char:56 + $searchApp | Set-SPEnterpriseSearchServiceApplication <<<< -DefaultContentAccessAccountNam $svcConfig.EnterpriseSearchServiceApplications.EnterpriseSearchServiceApplication.ContentAccessAccount ` + CategoryInfo : InvalidData (Microsoft.Offic...viceApplication:SetSearchServiceApplication)
[Set-SPEnterpriseSearchServiceApplication], InvalidOperationException FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.SetSearchServiceApplication
--------------------------------------------------------------
Get-SPEnterpriseSearchCrawlContentSource :
The search service is not able to connect to the machine that hosts the administration component.
Verify that the administration component '93c10c63-1bf5-45a8-90ae-a2f48e22f440' in search application 'Search Service Application' is in a good state and try again.
At C:\SP2010\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2767 char:85 + Get-SPEnterpriseSearchServiceApplication | Get-SPEnterpriseSearchCrawlContentSource <<<< |
Set-SPEnterpriseSearchCrawlContentSource -StartAddresses $CrawlStartAddresses + CategoryInfo : InvalidData: (Microsoft.Offic...wlContentSource: GetSearchCrawlContentSource)
[Get-SPEnterpriseSearchCrawlContentSource], I nvalidOperationException + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.GetSearchCrawlContentSource
--------------------------------------------------------------
New-SPEnterpriseSearchCrawlExtension :
The search service is not able to connect to the machine that hosts the administration component.
Verify that the administration component '93c10c63-1bf5-45a8-90ae-a2f48e22f440' in search application 'Search Service Application' is in a good state and try again.
At C:\SP2010\AutoSPInstaller\AutoSPInstallerFunctionsCustom.ps1:106 char:42 + New-SPEnterpriseSearchCrawlExtension <<<< -SearchApplication $searchApplication -Name "pdf" |
Out-Null + CategoryInfo : InvalidDa (Microsoft.Offic...hCrawlExtension: NewSearchCrawlExtension)
[New-SPEnterpriseSearchCrawlExtension], InvalidOperationException + FullyQualifiedErrorId : Microsoft.Office.Server.Search.Cmdlet.NewSearchCrawlExtension
--------------------------------------------------------------
First a Note of Caution:
The following procedure outlines my solution to this problem and should only be used at your own risk if you choose to do so. I am not responsible for any damages that may be done to your system as a result and I recommend you consult with a professional (and pay him/her well ) for your institution's unique IT needs. :)
Overview:
In my case these issues were caused by an un-installation followed by a re-installation of Microsoft SharePoint 2010. It's possible that the un-installation of the product left some resident files on the system or entries in the registry after the initial configuration . This could have affected the follow-up configuration of SharePoint after the re-installation. The following three simple steps will have Search Service up and running again… 1) Delete the current Search Service Application and data, 2) Add a new Search Service Application using Central Administration, 3) Complete the scripted installation of Microsoft SharePoint 2010 by launching AutoSPInstaller.bat.
1) Delete the current Search Service Application and Data:
Open your browser and navigate to Central Administration page http://localhost:port and select Manage Service Application. You should be logged in as Administrator or have privilege to delete and create service applications.

Click to select the entry labeled Search Service Application.




Verifly the data has been deleted by logging into your SQL Server Management Studio and verifying the SharePoint Database entries without GUID's have been deleted from your instance of SQL Server.

2) Add a new Search Service Application using Central Administration:



Add the SearchContentAccess domain account to run as a local service.

Create two new application pools for the 'Admin Web Service' and 'Query Web Service'. I previously created my application pools, so therefore mine already exist in the drop-down list. I recommend you select the option to create a new application pool and give your application pool a unique name that does not already exist in the drop-down menu.




Click on the text to view the Search Service Application.

If your Search Service Application page looks like this then you now have a correct pre-configuration.

Verify using SQL Server Management Studio that the new databases with the GUID extensions have been created on your instance of SQL Server .

3) Run AutoSPInstaller.bat to complete your scripted installation of SharePoint 2010 without error:
Completing the AutoSPInstaller.bat will finish the details of your configuration and add the correct adobe icon to your .pdf files when searching.

4) Celebrate!
If I have helped you please take one second to leave me a comment or say thank you. If the comments bar is not visible below please click here.