The indexing of mailbox database Mailbox Database 1759433534 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedForCorruptionException:
"Feeding was skipped for '48f0b7fa-ad8f-4e76-b10d-7f5f16024f6d (Mailbox Database 1759433534)' due to the state 'Failed', error code: 'CatalogCorruption', failure code: '4321345', failure reason: 'Journal has been detected as invalid.'."
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.SyncRootController.ExecuteComplete(IAsyncResult asyncResult)
The indexing of mailbox database Archive encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedForCorruptionException:
"Feeding was skipped for 'f43b8d9d-7ae9-4bb8-8c82-577aa44bac09 (Archive)' due to the state 'Failed', error code: 'CatalogCorruption', failure code: '4321345', failure reason: 'Journal has been detected as invalid.'."
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.SyncRootController.ExecuteComplete(IAsyncResult asyncResult)
Another error:
The FastFeeder component received a connection exception from FAST. Error details: Microsoft.Exchange.Search.Fast.FastConnectionException: Connection to the Content Submission Service has failed. ---> Microsoft.Ceres.External.ContentApi.ConnectionException:
Recovery failed after 0 retries
at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder.CheckRecoveryFailed()
at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder.SubmitDocument(Document document, TimeSpan timeout)
at Microsoft.Ceres.External.ContentApi.DocumentFeeder.DocumentFeeder.SubmitDocument(Document document)
at Microsoft.Exchange.Search.Fast.FastFeeder.SubmitDocumentInternal(Object state)
--- End of inner exception stack trace ---
When I check the process it seems its bouncing between healthy and upgrading, crawling, failed, failed and suspended, back to failed, crawling, etc etc.
In perfmon you can see some changes, but mailboxes remaining are still max and not counting down.
Items sent for processing and rate of attempted items Submission are both counting and then reset back to 0 after a time.
It's seems the system the process keeps failing and stuck in a loop.
It's also draining the server resources, the server is very slow.
Update: It seems the loop is over:
Final state: FialedAndSuspended
Perfmon crawling monitoring is all set to 0.
