SharePoint 2013 Search Error "Unable to retrieve topology component health. This could be because the admin component are not up and running "

Environment description

　　Windows R2,sharepoint 2013 (no SP1 patches), SQL Server 2012

Error description

The search service is fine, but the crawl has been crawling full, but nothing has been crawled and will not stop and crawl all night without crawling to:

Crawl not only, climbed a night nothing crawled, error is as follows:

Go to 15/logs inside to look for the diary;
Non-oauth request. Isauthenticated=true, Useridentityname=0#.w|domain\user, claimscount=125b5b2d49c-feb7-e08b-ecf7-28204da68508

UserAgent not available, file operations may is not optimized. At Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer (Spfilestreamstore SPFs, ILockBytes ILB, Boolean Copyonfirstwrite, Boolean disposeilb) at Microsoft.SharePoint.SPFileStreamManager.SetInputLockBytes ( spfileinfo& FileInfo, sqlsession session, Prefetchresult Prefetchresult) at Microsoft.SharePoint.CoordinatedStrea MBuffer.SPCoordinatedStreamBufferFactory.CreateFromDocumentRowset (Guid DatabaseId, sqlsession session, Spfilestreammanager spfstm, object[] metadatarow, Sprowset contentrowset, spdocumentbindrequest& dbreq, spdocumentbindresults& dbres) at Microsoft.SharePoint.SPSqlClient.GetDocumentContentRow (Int32 Roword, Object Ospfilestmmgr, spdocumentbindrequest& dbreq, spdocumentbindresults& dbres ...

The crawler could not communicate with the server. Check the the server is available and that the firewall access is configured correctly.

Event Viewer error;
Webhost failed to process a request.
Sender information:system.servicemodel.servicehostingenvironment+hostingmanager/63363381
Exception:System.ServiceModel.ServiceActivationException:The Service '/90ac4adbb96a4e89892b2ad7ab02da51/  Metadatawebservice.svc ' cannot is activated due to an exception during compilation. The exception message Is:the Farm is unavailable. ---> System.InvalidOperationException:The farm is unavailable.
At Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceManager.get_Local ()
At Microsoft.SharePoint.IdentityModel.SPServiceIssuerNameRegistry. ctor ()
At Microsoft.SharePoint.SPServiceHostOperations.Configure (ServiceHostBase serviceHost, Spserviceauthenticationmode Authenticationmode)
At Microsoft.SharePoint.Taxonomy.MetadataWebServiceHostFactory.CreateServiceHost (String constructorstring, uri[] baseaddresses)
At System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService (String Normalizedvirtualpath, Eventtraceactivity eventtraceactivity)
At System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService (serviceactivationinfo Serviceactivationinfo, eventtraceactivity eventtraceactivity)
At System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable (String Normalizedvirtualpath, eventtraceactivity eventtraceactivity)
---End of inner exception stack trace---
At System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable (String Normalizedvirtualpath, eventtraceactivity eventtraceactivity)
At System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast (String Relativevirtualpath, Eventtraceactivity eventtraceactivity)
Process name:w3wp
Process id:6004

Workaround

Event Viewer error, refer to the following link to resolve, but not solve the crawl problem:

https://social.technet.microsoft.com/Forums/en-US/ef415574-2e89-4fd9-8538-c49eef3366c6/ searchservicesvc-cannot-be-activated-due-to-an-exception-during-compilation-the-exception?forum= Sharepointsearch

After a day of struggle, finally decided to delete the search service, rebuild! After the reconstruction, found that the error is more serious, the Search host Control service is not connected; Then, the Search host Control Service, the discovery and search service running account is not a, updated into one later, the search service is normal, crawl network is no problem!

Other references

　　Solve the process, found that other people have encountered similar problems, and their reasons are different, the remarks below give you a reference;

http://blog.csdn.net/abrahamcheng/article/details/11216087

SharePoint 2013 Search Error "Unable to retrieve topology component health. This could be because the admin component are not up and running "