Recently one of the exchange servers had a unforeseen reboot and after that the content index state would not go healthy but kept reporting as failed. In event viewer the following was logged every few minutes:

Event ID: 1012

Exchange Server Information Store has encountered an error while executing a full-text index query (“eDiscovery search query execution on database <guid> failed.”). Error information: System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:3847/. The connection attempt lasted for a time span of 00:00:02.0821592. TCP error code 10061: No connection could be made because the target machine actively refused it —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it


To fix this we have to go through a few steps.

  • Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.

Navigate to the following directory:

  • C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data\Nodes\Fsis

Delete all the files in the Fsis folder (make a backup just-in-case)

Open up the Exchange Management Shell (Elevated)

  • Navigate to directory C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer

Run the following command, it will re-create the folders we deleted:

  • .\installconfig.ps1 -action I -datafolder “c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data”

After this command has completed, start the search service. You can force AD Replication or wait for it. After that it should report in event viewer that indexing has started successfully.

If the above didn’t work then you will need to uninstall the search component and then re-install it. First stop the services again.


  • .\installconfig.ps1 -action U -datafolder “c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data”


  • .\installconfig.ps1 -action I -datafolder “c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data”

Start the services again and then monitor the event log for indexing has started and completed successfully. You can also check by running a Get-MailboxDatabaseCopyStatus in the EMS to view the content index state.

Hope it helps.

Discover more from COLLABORATION PRO

Subscribe now to keep reading and get access to the full archive.

Continue reading