none
Search Host Controller service has stopped working RRS feed

  • Question

  • Hello,

    I manage several single-server- and small-scale-Sharepoint Farms. They are all within the same domain/forest and managed the same way.

    One of them has developed an issue two weeks ago - the Sharepoint Search Host Controller service has stopped working all of a sudden. This has happened on one Sharepoint farm only - all others (about a dozen) are working absolutely fine. The service cannot be started again. When you try, you get the error message: "Error 1067: The process terminated unexpectedly".

    The error message in the Event Viewer says the following:

    Event ID 1000:

    Faulting application name: hostcontrollerservice.exe, version: 15.0.4937.1000, time stamp: 0x591a9476
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.24535, time stamp: 0x5dc1e835
    Exception code: 0xe0434352
    Fault offset: 0x000000000000b87d
    Faulting process id: 0x11e0
    Faulting application start time: 0x01d5b41de88e3f2c
    Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\HostController\hostcontrollerservice.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: 285e481a-2011-11ea-bf83-901b0e109035

    Event ID 1026:

    Application: hostcontrollerservice.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.Collections.Generic.KeyNotFoundException
    Stack:
       at Microsoft.Ceres.HostController.Service.ServiceRunner.Initialize()
       at Microsoft.Ceres.HostController.Service.ServiceRunner.HostControllerStarter()
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Threading.ThreadHelper.ThreadStart()

    The Sharepoint log unfortunately doesn't go much beyond that. The key phrase that is being repeated is this:

    Exception Info: System.Collections.Generic.KeyNotFoundException

    Unfortunately I have no idea what this means or what I could do. The OS-admins tell me that there were no changes on the server or with Group Policies/Local Policies/anything else.

    What I have tried so far:

    - Rebooting (obviously)

    - The Sharepoint Wizard

    - Using another account to start the service (up to farm account or Local System)

    - Installing the latest patches (in the hopes that this was a product error)

    - A repair installation of Sharepoint from the Control Panel

    Nothing works and I am a bit lost. This is a production system, so "reinstalling from scratch" isn't really an option I can suggest lightly. The broken service causes the Search and the connected Office Online Server (WOPI) to fail.

    The system is a Windows Server 2008 R2, SQL Server 2012, Sharepoint Server 2013 SP1 with the October 2019 CU. And yes, I know that Windows Server 2008 R2 is almost out of support.  :)

    If anyone has any ideas...

    Tuesday, December 17, 2019 8:45 AM

Answers

  • Hi aziegler,

    I would suggest you open a ticket with microsoft so they will support you better. You would get more help there.

    Besides, If my reply is helpful to you, please mark it as an answer. Thanks for your understanding.

    Best Regards,

    Emily Du



    Thursday, December 19, 2019 10:23 AM

All replies

  • first, make sure your minRole include search role.

    second, you can start the service in server service list in control panel.


    Please remember to mark the replies as answers if they helped.
    Linyu - SharePoint Engineer
    QQ Group: 72637444

    Wednesday, December 18, 2019 7:47 AM
  • Hi aziegler,

    Please do the following steps to troubleshooting this issue:

    1. Start the SharePoint Search Host Controller Service in windows services with the farm account, and check whether the farm account’s password is right.

    2. Check Net. Tcp Port Sharing ServiceNet. Tcp Listener Adapte ServiceRemote Registry Service and Appfabric Caching Service are running normally in the windows services.

    3. Go to CA > Security -> Configure Service Accounts -> select Windows Service – Search Host Controller Service, check if the account is correct.

    4. Find Node.ini files through the path: C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Applications\Search\Nodes\{search components}\Configuration\Local, check the Node.ini files of the five components.

    Reference: https://blogs.technet.microsoft.com/saantil/2013/10/03/search-host-controller-service-and-content-processing-service-on-sharepoint-server-is-down-sharepoint-2013/

    5. Create a new search service application then start the SharePoint Search Host Controller Service.

    Here are some similar articles about how to solve your issue:

    http://sensoft2000-sharepoint.blogspot.com/2013/12/search-service-host-controller-struck.html
    https://danmyhre.wordpress.com/2015/03/07/search-host-controller-service-stuck-in-starting/
    https://guidesharepoint.wordpress.com/2017/12/24/hostcontrollerservice-exe-not-being-able-to-start-up-in-sharepoint-2013/

    Best regards,

    Emily Du

    Wednesday, December 18, 2019 8:13 AM
  • Hello Linyu,

    this is Sharepoint 2013, it doesn't have "MinRole".

    And I tried starting the service via the administrative tools, but that doesn't work.

    Wednesday, December 18, 2019 8:18 AM
  • Hello Emily,

    thank you for your suggestions! Here is what happened:

    1.) I tried that, it had no effect at all. Same error.

    2.) All these services are running fine.

    3.) Account and password are correct.

    4.) The node.ini looks fine

    5.) I cannot do this. There is a custom-built application on the Sharepoint that uses the Search Application. If I remove the old search application, I basically break this custom-built application.

    Is there a way to find out what this "Generic Key not found"-error means or where/why it is triggered?

    Wednesday, December 18, 2019 9:15 AM
  • Hi aziegler,

    I would suggest you open a ticket with microsoft so they will support you better. You would get more help there.

    Besides, If my reply is helpful to you, please mark it as an answer. Thanks for your understanding.

    Best Regards,

    Emily Du



    Thursday, December 19, 2019 10:23 AM
  • Hi aziegler ,

    I am looking forward to your feedback if there is any update.

    Best regards,

    Emily Du

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Monday, December 23, 2019 1:17 AM
  • Hello Emily,

    it seems I have no choice but to open a ticket with Microsoft on this one...

    Thanks to everyone who read this and made suggestions though! Really appreciated!  :)

    Tuesday, January 7, 2020 11:37 AM