Hello,
We have been running Exchange 2013 CU7 with DAG since early this year and no issues. Last weekend I upgraded to CU10 and now I am seeing errors on one of the server where all the copies remain passive.
Usually I have seen this event if before when we failover and restart the server but now it just comes while everything running normally. This error message has this line "The Content Submission Service returned failure for the document: Document timeout expired" which is different than those message which I see during failover. I restart Microsoft Exchange Search service and everything again goes to normal then after some time again I see this error.
Get-MailboxDatabaseCopyStatus shows "ContentIndexerrormessage" "Failed an Internal error occurred for the database or its index".
This occurred on different database sometimes multiple databases. Restart of search service fixes it for some time.
https://support.microsoft.com/en-us/kb/2807668
I am aware of this link but my error message is slightly different as I mentioned above and restart of search fixes it for a short time.
Log Name: Application
Source: MSExchangeFastSearch
Date: 11/9/2015 12:20:31 PM
Event ID: 1009
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: Server2.company.com
Description:
The indexing of mailbox database MDB_Name1 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException:
The component operation has failed. ---> Microsoft.Exchange.Search.Fast.FastDocumentTimeoutException:The Content Submission Service returned failure for the document: Document timeout expired
. ---> System.TimeoutException: Document timeout expired
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Fast.FastFeeder.EndSubmitDocument(IAsyncResult asyncResult)
at Microsoft.Exchange.Search.Mdb.RetryFeeder.DocumentCompleteCallback(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
at Microsoft.Exchange.Search.Engine.SearchFeedingController.ExecuteComplete(IAsyncResult asyncResult)
--- 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)
====================
Is anyone else is aware of what could be the issue after CU10.
Thanks,
Raman