Hello,

Search was working perfectly but all of sudden it stopped working. When I check the search service application then I got the following error 

"Unable to retrieve topology component health states. This may be because the admin component is not up and running."

I checked the permission of the service account, it is set to "SPSearchDBAdmin".

Can anyone help me out? Thanks in advance.

Are you opening the search service application with farm account. Also can you check if admin component is showing up and running:

If its down, it may be because of many reasons like drive is full, or not available. Or it may be simple because enough RAM is not available.

Hope this helps.

Hi Rohit,

Just check any password changes to this account has happened ? or application pool account on IIS has started and running .
Restart if its not started and ensure the application pool account uses the "SPSearchDBAdmin". And also ensure the Search Administration DB is connected with your SP Farm.

To get more precise information on this problem, check the event viewer and SharePoint log.

No its not showing like the one you shared, previously it was showing like that.

But now only database names are showing. Its not showing the tick marks. I'm unable to share the screenshot here because of msdn verification.

Hi Murugesa, I checked that no one has changed the password for that account. Also checked the application pool & it in running state. Don't understand why it stopped suddenly :(

Can you check the ULS logs, what is the error related to search being logged in there. By default, ULS logs are stored in "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS" folder.

Hi Rohit,

First you need to find out if the problem is with Search service application or the web application for which you have to do little isolation.

1) When you browse searchadministration.aspx do you see all the components with green checks? If not then there is an issue with your search SA

2) If there is an issue with components then open the task manager and see if you are seeing 5 noderunner.exe if not restart search host controller service from services.msc

3) If your search is fine which is less likely then create a new web application and try crawling the new web application and see how it behaves

and you can also verify if

Are you aware of any infrastructure changes as of late? 
These might include: -

1.Patches or product installation or configuration
2.Search Service account permissions might have bee changed
3.Firewall changes or configurations

Please mark the answer and vote me as helpfull if you think it will resolved your issuse

Regards

Anil

• Edited by AnilSharma4 20 hours 54 minutes ago added more info..

Hi Mohit,

Its not showing any corelation ID. Its only showing 0000000000 as the corelation ID. Here is the entry in the logs

MessageQueue : Enqueuing 59636: NodeUnavailable: 'QueryProcessingComponent1 [a47ad7d5-bac2-442c-8932-01159ef3a974]' found 'ServiceLocation[net.tcp:///9C3F38/AdminComponent1/Services/InvokerService 2]' to be unavailable
Microsoft.Ceres.CoreServices.Node.NodeController : Unable to reach system manager at: net.tcp:///9C3F38/AdminComponent1/Services/InvokerService : Microsoft.Ceres.CoreServices.Services.Container.StaleServiceReferenceException: Remote invocation stop retrying after communication failure (service=Microsoft.Ceres.CoreServices.InternalServices.SystemManager.ISystemManager method=get_Primary location=ServiceLocation[net.tcp:///9C3F38/AdminComponent1/Services/InvokerService 2]) ---> System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception. ---> System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The system cannot contact a domain controller to service...  

Hi,

I would suggest you to go through the "Health monitoring" report on your Central Administration and the Event log the server where this error reporting.

Please copy the error message here, so we can help you to troubleshoot.

Hi Anil Sharma, I checked the noderunner process in task manager. It is not running in the task manager. I restarted the "search host controller service" but still noderunner didn't start.

Also there are no green checks in searchadministration.aspx. So what might be the exact problem because search was working fine but all of sudden it stopped working.

Hi Rohit,

First you need to find out if the problem is with Search service application or the web application for which you have to do little isolation.

1) When you browse searchadministration.aspx do you see all the components with green checks? If not then there is an issue with your search SA

2) If there is an issue with components then open the task manager and see if you are seeing 5 noderunner.exe if not restart search host controller service from services.msc

3) If your search is fine which is less likely then create a new web application and try crawling the new web application and see how it behaves

and you can also verify if

Are you aware of any infrastructure changes as of late? 
These might include: -

1.Patches or product installation or configuration
2.Search Service account permissions might have bee changed
3.Firewall changes or configurations

Please mark the answer and vote me as helpfull if you think it will resolved your issuse

Regards

Anil

• Edited by AnilSharma4 Monday, August 24, 2015 10:43 AM added more info..

You should be checking more on this error:

System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. ---> System.ComponentModel.Win32Exception: The system cannot contact a domain controller to service...

Check more on the network configuration on the server and its connectivity to domain controllers in your domain. I don't believe search is at issue here. You can also try restarting server to see if it helps.

Thank you very much Mohit. I'll check the connectivity to domain controllers and will let you know the further details.

Hi Rohit,

Any update?

Thanks,

Patrick Liang