ExchangeFastSearch errors 1010 but Content index state: Healthy

Question

_{Thursday, August 17, 2017 7:20 AM}

Having a strange issue, new Exchange 2016 server, searched in OWA not working but Exchange reports the databse status as  "Content index state: Healthy"

The application log is full of the following error

Source: MSExchangeFastSearch

The description for Event ID 1010 from source MSExchangeFastSearch cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. > System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://localhost:3803/Management/IndexController that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Server stack trace: 
   at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Ceres.SearchCore.Admin.IIndexManagement.get_IndexSystemNames()
   at Microsoft.Exchange.Search.Fast.IndexManager.<GetCatalogs>b__1a(IIndexManagement agent)
   at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[TManagementAgent,TResult](AgentHandle`1 agentHandle, Func`2 function, String eventLogKey)
    End of inner exception stack trace

the message resource is present but the message is not found in the string/message table

ant help would be aprecaited

All replies (1)

_{Friday, August 18, 2017 9:01 AM}

Hi,

Thanks for contacting our forum.

Given the error message as following:

at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper)    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.SendPreamble(IConnection connection, ArraySegment`1 preamble, TimeoutHelper& timeoutHelper)    at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.DuplexConnectionPoolHelper.AcceptPooledConnection(IConnection connection, TimeoutHelper& timeoutHelper)    at System.**ServiceModel.**Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)    at System.**ServiceModel.**Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)    at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)    at System.**ServiceModel.**Channels.ServiceChannel.OnOpen(TimeSpan timeout)    at System.**ServiceModel.**Channels.CommunicationObject.Open(TimeSpan timeout)    at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)    at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)    at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)    at System.**ServiceModel.**Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)    at System.**ServiceModel.**Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)    at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

It seems it’s related to the services, please make sure the services below is running correctly, especially the Microsoft Exchange Search Host Controller services:

• Microsoft Exchange Search 
• Microsoft Exchange Search Host Controller

From the error below message:

at Microsoft.Ceres.SearchCore.Admin.IIndexManagement.get_IndexSystemNames()    at Microsoft.Exchange.Search.Fast.IndexManager.<GetCatalogs>b__1a(IIndexManagement agent)

The issue seems also related the search index, it’s recommended to recreate the search index manually and check the results:

Refer to: https://blogs.technet.microsoft.com/exchangesearch/2013/10/28/rebuild-an-index-on-exchange-2013-for-specific-databases/ it’s also used to Exchange server 2016.

Hope it helps.

Regards,

Jason Chao

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].