We are running exchange 2013 with 2 servers in a DAG. On one of the servers we are getting error messages in the event log to do with the search function.

Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The
component operation has failed. --->
Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped
for 'b0d55635-e3d9-4d83-9661-d7379e1cf0b0 (MDB01)' due to the state 'Unknown',
error code: 'Unknown'." at
Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
at
Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object
state) --- End of inner exception stack trace --- at
Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult
asyncResult) at
Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult
asyncResult)

When someone attempts a search which uses the server we get the following message.

Exchange Server Information Store has encountered an error while executing a full-text index query ("string("mark*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

I have looked on the internet for a solution and so far nothing has helped the issue.  I've looked at the content submitters group but I would have thought it would have effected both servers and not just 1.

I've run the script to install the search foundation service but this has not resolved the issue.

Has anyone come across the errors both and resolved the issue?

Thanks

Chris

I hope that below mentioned articles would help you to resolve content indexing issue, kindly Mark as answered if you are able to resolve the issue.

http://blogs.technet.com/b/exchange/archive/2011/01/18/3411844.aspx

http://blogs.technet.com/b/mspfe/archive/2012/04/27/how-to-troubleshoot-issues-with-exchange-2010-search.aspx

http://msexchangeguru.com/2010/12/01/cannot-activate-database-copy-content-index-catalog-files-in-failed-state/

• Proposed as answer by Rajkumar Nagaraj Monday, March 02, 2015 10:30 AM

I've had a look at the articles but these have not worked for me.  When I've run the troubleshooter-ci1 script it throws an exception cnouldn't read registry key: SOFTWARE\Microsoft\ExchangeServer\V15\ContentIndex\CatalogHealth\

I've checked the registry manually and the key from ContentIndex does not exist on either server including the one working.

Hi,

Please check the content index status of databases in DAG. If it's unhealthy, please rebuild content index to check result.

Best regards,

Follow the below mentioned technet article to rebuild content indexing

https://technet.microsoft.com/en-in/library/aa995966%28v=exchg.80%29.aspx?f=255&MSPPError=-2147217396

Thanks everyone for the replies.

Over the weekend we run the outstanding windows updates on the exchange server and this surprisingly fixed our issue.  The unknown state change to failedandsuspended and after a few hours went to healthy. 

The updates were done as part of a chance maintenance window and wasn't expecting this to have an effect. 

Regards

Chris