Hello all,

i checked all solutions from technet i found to this problem, but nothing helped

My environment:

2x Exchange 2013 CU7 with DAG Cluster, one 700GB Database, all Mailboxes migrated some months ago from Exchange 2010

The passive Copy has always "failed an Suspended" Content Index State after failover

I always get eventlog error MSExchangeFastSearch 1013 & 1009 when I try to rebuild the content index

1013: Indexing state not found in FAST catalog for MDB 78A30F80-896D-4E4E-91CA-C792E02F60BC12

1009: The indexing of mailbox database MBXDB1 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.CatalogReseedException: The database '78a30f80-896d-4e4e-91ca-c792e02f60bc (MBXDB1)' needs to be crawled but is not mounted on the preferred active server. Requesting a reseed.

   bei Microsoft.Exchange.Search.Engine.SearchFeedingController.PrepareToCrawl(NotificationsEventSourceInfo ciWatermarkInfo)

   bei Microsoft.Exchange.Search.Engine.SearchFeedingController.DetermineFeederStateAndStartFeeders()

   bei Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   bei Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- Ende der internen Ausnahmestapelberwachung ---

   bei Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   bei Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)

What i tried:

• rebuild passive Content Index with update-mailboxdatabasecopy catalogonly
• Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller. Delete Content Index Folder in filesystem. start the services
• Adding Contentsubmitters group ((http://support.microsoft.com/kb/2807668))
• rebuild the DAG copy, not only the catalog:  Database update-mailboxdatabasecopy deleteexistingfiles
• check activationpreference via ECP und Powershell. The passive copy has preference 2, the active copy preference 1

Especially I dont understand the activationpreference error

thank you in advance Boris

 

Hi,

Did you try to force restart Replication Service?

Please try to run Get-MailboxDatabaseCopyStatus to check whether all node are healthy.

 

Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi Mavis,

this problem exists since december. I made many reboots and also an upgrade CU3 -> CU7

 Here's Get-MailboxDatabaseCopyStatus from the passive server

Name                                          Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
                                                              Length    Length                             State
----                                          ------          --------- ----------- --------------------   ------------
MBXDB1\EXCH201301                             Healthy         0         2           10.03.2015 09:22:58    FailedAnd...
MBXDB2\EXCH201301                             Healthy         0         0           09.03.2015 17:51:51    Healthy
MBXDB3\EXCH201301                             Healthy         0         0           09.03.2015 17:14:31    Healthy
MBXDB4\EXCH201301                             Healthy         0         0           09.03.2015 17:59:39    Healthy

There's a procedure in this Technet article that might help. Particularly the log events would be interesting. Also it would be good to turn up the logging on this specific category of logs, however I'm not sure if Set-EventLogLevel will achieve this.

Finally, in Exchange 2010 there were a couple of Exchange troubleshooters specifically created for index corruption. Troubleshoot-CI.ps1 still exists in Exchange 2013's scripts directory, however running it throws an exception. According to the article here, this is due to a regkey that no longer exists, so most likely won't lead anywhere.

Hi,

we decided to create new databases and move all mailboxes to the new databases.

the new databases don't have the same problem, so my problem is solved

rg. Boris

• Marked as answer by Boris Birneder 17 hours 44 minutes ago