Dears,
I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only
my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers
The following is the errors and warnings logs on my effected mailboxes servers:
The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' 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)
The FastFeeder component received a connection exception from FAST. Error details: 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:
Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)
at SyncInvokeGetItems(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log
-------------------------------------------------------------------------------------------------------------------------------------
An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.
Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
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.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()
at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)
at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()
at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()
at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)
--- End of inner exception stack trace ---
------------------------------------------------------------------------------------------------------------------------------------
Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", 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:
Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)
at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
What i have tried to solve the issue with no luck is:
1- Reseed the effected Databases
2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index
3- Restart the mailbox server that has the index issue
4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668
Any Idea will be much appreciated.
Thanks,
Ayman Saleh
Ayman Saleh