Hello community,

I have a farm with 2 mermber servers (SPsvr1 and SPsvr2). On SPsvr1 the "SharePoint Search Host Controller" is running normally, but it is not running on SPsrv2. When I try to start it I receive the following error:

The error logs that appear in the event viewer are the following:

Event ID: 1026

Event ID 1000:

Event ID 8230:

Event ID 1001:

I have been looking for a solution for almost 3 weeks, and I found that in the SPsvr1 exist a directory that does not exist on SPsvr2. The directory is: "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search". I copied that directory from SPsvr1 to SPsvr2 but it did not make any change, the errors continue being the same.

I cannot configure a search service application because that service does not start on the SPsvr2 s

try to add the Search Services account into local admin on the bad server and then reboot it and try again.

also make sure the settings in the registry as mentioned here:

http://forums.anandtech.com/showthread.php?t=20850

try to add the Search Services account into local admin on the bad server and then reboot it and try again.

also make sure the settings in the registry as mentioned here:

http://forums.anandtech.com/showthread.php?t=20850

did y

Hi Melvintt,

According to your description, my understanding is that you got an error when you started SharePoint Search Host Controller.

I got a similar error with you when I started the service. I clicked the service properties, selected Log on tab, then selected This account, re-typed the service account (note: I have changed the password ), then I could start the service. Please check your service account.

Also , here are some similar posts for you to take a look at:
http://blogs.technet.com/b/saantil/archive/2013/10/03/search-host-controller-service-and-content-processing-service-on-sharepoint-server-is-down-sharepoint-2013.aspx
http://msscorner.de/en/2012/11/14/search-host-controller-hung-on-starting-in-sharepoint-2013/

I hope this helps.

Thanks,

Wendy

Hi Melvintt,

According to your description, my understanding is that you got an error when you started SharePoint Search Host Controller.

I got a similar error with you when I started the service. I clicked the service properties, selected Log on tab, then selected This account, re-typed the service account (note: I have changed the password ), then I could start the service. Please check your service account.

Also , here are some similar posts for you to take a look at:
http://blogs.technet.com/b/saantil/archive/2013/10/03/search-host-controller-service-and-content-processing-service-on-sharepoint-server-is-down-sharepoint-2013.aspx
http://msscorner.de/en/2012/11/14/search-host-controller-hung-on-starting-in-sharepoint-2013/

I hope this helps.

Thanks,

did you try to find this way Unprovisioning

also try from Central admin, start the Services from the services on server.

if it stuck at starting, then try this:

http://blog.mwiedemeyer.de/post/2012/10/11/Search-Host-Controller-Service-in-Starting-state

did you try to find this way Unprovisioning

1 2 3 4

$SA = Get-SPServiceInstance | Where {$_.Status -like Unprovisioning} $SA.Unprovision()   $SA.Provision()

also try from Central admin, start the Services from the services on server.

if it stuck at starting, then try this:

http://blog.mwiedemeyer.de/post/2012/10/11/Search-Host-Controller-Service-in-Starting-sta

could you please check if Usage Application Proxy is running if not

$UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"}
$UP.Provision()

Hi Melvintt,

i had the same issue (On Sharepoint 2013 foundation).

I made sure that the below 2 services are up and running in your case, if they are running i would suggest you to restart the below services and then try starting the "SharePoint Search Host Controller"

Net.Tcp Listener Adapter
Net.Tcp Port Sharing Service

Thanks,
Satyam

could you please check if Usage Application Proxy is running if not

$UP = Get-SPServiceApplicationProxy | where {$_.TypeName -like "Usage*"}
$UP.Provision()		

Hi Melvintt,

i had the same issue (On Sharepoint 2013 foundation).

I made sure that the below 2 services are up and running in your case, if they are running i would suggest you to restart the below services and then try starting the "SharePoint Search Host Controller"

Net.Tcp Listener Adapter
Net.Tcp Port Sharing Service

Thanks,
Satyam

Hello Satyman,

I restarted both services you mentioned and then restarted the Sharepoint Search Host controller, but nothing happened. I still do not see the topology.

Hi Melvintt,

just asking... the account which we are using is a domain account right ..?
When we restarted the server, the status of the service, was it stopped or stopping ..?
Did we use the powershell script to create the service application?

////////////////////////////////////////////////////////////////////////////////////////////////

When did we receive the  Error message which you placed (which  is as below)

Event ID 8230:

Volume Shadow Copy Service error: Failed resolving account administrator with status 1376. Check connection to domain controller and VssAccessControl registry key. 

////////////////////////////////////////////////////////////////////////////////////////////////

Thanks,
Satyam

Hi Melvintt,

just asking... the account which we are using is a domain account right ..?
When we restarted the server, the status of the service, was it stopped or stopping ..?
Did we use the powershell script to create the service application?

////////////////////////////////////////////////////////////////////////////////////////////////

When did we receive the  Error message which you placed (which  is as below)

Event ID 8230:

Volume Shadow Copy Service error: Failed resolving account administrator with status 1376. Check connection to domain controller and VssAccessControl registry key. 

////////////////////////////////////////////////////////////////////////////////////////////////

Thanks,
Satyam

Hi Satyman,

Yes, the account is a domain account. When I restarted the server the status of the service was Stopped, but after I did the solution Waqas Sarwar told me now the status is Started. I did not use PowerShell to create the Search Service Application, I instead used Central Admin.

We received the error with Event ID 8230 when the service couldn't start, but now that the service is running that error is not present.

could you please make sure no extra white space in the Environment variable

http://blogs.msdn.com/b/sambetts/archive/2013/08/28/sp2013-win2012-unable-to-retrieve-topology-component-health-states-this-may-be-because-the-admin-component-is-not-up-and-running.aspx

could you please make sure no extra white space in the Environment variable

http://blogs.msdn.com/b/sambetts/archive/2013/08/28/sp2013-win2012-unable-to-retrieve-topology-component-health-states-this-may-be-because-the-admin-component-is-not-up-and-running.as

check this one :http://blogs.technet.com/b/steve_chen/archive/2013/05/23/357438

Hi Melvintt,

According to your description, my understanding is that there was not the search application topology on any your Sharepoint server.

There are many reasons for this issue. Please try to repair SharePoint under Control Panel, compare the result.

Whether you have a dedicated search server for your SharePoint. If yes, please check its connections to DC server and SharePoint server.

Here are some similar posts for you to take a look at:
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/424f3f43-aab7-4efd-8b0e-5bc28bd27e66/unable-to-retrieve-topology-component-health-states?forum=sharepointsearch
http://aseempandit.wordpress.com/2013/12/24/unable-to-retrieve-the-search-application-topology/
http://social.technet.microsoft.com/Forums/en-US/539cada1-181b-4af7-9e2a-4d6f9b1700c8/search-topology-not-displayed?forum=sharepointsearch

I hope this helps.

Thanks,

Wendy