I have installed Exchange 2013 CU8 on Windows 2012 in coexistence with Exchange 2007 SP3 Rollup 16 and as soon as I installed the MBX roles (2 servers) the default databases came with Unknown index state.

I have followed this article https://support.microsoft.com/en-us/kb/2807668 and restarted the servers which brought the DB to healthy again but after couple of minutes it fails once again. 

Is this a bug on Exchange 2013 CU8 with Windows 2012? Because I already installed it on 2012 R2 and I didn't have this issue.

I would appreciate any suggestions or comments.

Hello

tip:

stop Microsoft Exchange Search Host Controller, and Microsoft Exchange Search  services.

delete/rename catalog folder and start again services and check application eventlog

I did this but it didn't work. i rebuild the whole search services from scratch too and it didn't work. I have had this same problem in at least 5 deployments. 

Is there any way to solve it? 

I did this but it didn't work. i rebuild the whole search services from scratch too and it didn't work. I have had this same problem in at least 5 deployments. 

Is there any way to solve it?

Hello

In application log havent got error/warming message?

It's very interesting situation, I have 4 servers in total 2 CAS and 2 Mailboxes. 

After I add the two Mailbox server roles to DAG, it works properly and it Content Index state shows Healthy but then after 15 minutes it reports unknown on the ECP (Web Admin Panel) however when I check on Exchange mailbox server 1 it reports healthy. 

Could this be Active directory issue or is it general connectivity problem? We are using a proxy server in a strict environment. (BANK) .

Hi,

According to your description, I understand that one DAG members Content Index state shows Healthy but then after 15 minutes it reports unknown.
If I misunderstand your concern, please do not hesitate to let me know.

Please run below command to get details about your DAG cluster:
Get-HealthReport -Server "MB1" | where {$_.HealthSet -eq "Search"} | FL
Get-HealthReport -Identity MB1

If it display unhealthy, please run below command to check system component for Exchange server:
Get-ServerComponentstate -Identity servername

If the state is Inactive, please run below command to active relevant component:
Set-ServerComponentState <Identity> -Component component name -Requester HealthAPI -State Active
More details about Server Component States in Exchange 2013, please refer to:
http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx

meanwhile, please refer to Belindas answer for further troubleshooting:
https://social.technet.microsoft.com/Forums/office/en-US/49430658-37ae-47a6-a79f-146ed54c00cc/exchange-2013-databases-content-index-state-is-unknown?forum=exchangesvrgeneral

Thanks

Hi Allen,

the following command reports unhealthy on my both mailbox servers, I am attaching snapshot for you

Get-HealthReport -Server "mbxsrvr1" | where {$_.HealthSet -eq "Search"} | FL

Get server component state reports all active except two (ForwardSyncDaemon) and ProvisioningRps. I started those services with the command you posted as well but still the databases content Index are not reporting healthy .. it's still unknown.

I have tried disabling the CI for the databases using this command "Set-MailboxDatabase "Mailbox Database #" -IndexEnabled $false" then restarted services after I deleted the Index folders and it reports healthy but after about half an hour it reports unknown again. and the only errors reporting are the fast search 1009 and 1010, I am posting the error as well

The indexing of mailbox database DB01MBX01 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 'e88bd850-7fe0-4e3b-a12f-bf811b3a4677 (DB01MBX01)' 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)

and this

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.Close(Guid flowIdentifier)
   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlowAndGetResultCollection(String flowName, IEnumerable`1 inputData, String outputName)
   at SyncInvokeExecuteSearchFlowAndGetResultCollection(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.ImmutableDisp...).

I tried rebuilding the Search and search host services from scratch but that didn't work either 

I really have ran out of options and I would appreciate your support before I come to the consideration of rebuilding the whole environment. 

Thanks a lot