Hi,
I ran into a problem with our 2013 Exchange server CU14. When checking MailboxDataBaseCopyStatus, all our databases had ContentIndexState "failed". I found an article that showed me how to rebuild the contentindexdatabase.
The procedure was to stop "Microsoft Exchange Search Host Controller" and "Microsoft Exchange Search". Delete the content index located with the database. After deletion restart the services.
This worked on 2 out of 3 databases. Now we have 1 database still crawling, and it has been doing that for days now. When checking the index of the crawling database. I see that it has 9 databases to crawl, and index errorcode 3. This has been like this for days. After the crawl index seems to stop growing in size (checked the GUID.single folder), we also get an error in Event Viewer saying that Microsoft Exchange Search Server service terminated unexpectedly. This now happens every minute. The server is under heavy CPU load as the noderunner is taking a lot of CPU.
I just did another rebuild of the crawling database, but it seems to have stopped at the same mailbox as it still has 9 mailboxes to crawl.
I read somewhere from a guy that had a similar problem, that one of his user a problem and was causing the mailbox to stay in an endless crawling loop. Is there a way to find out which mailbox the crawling is currently at?
Is there anything else i should check to solve this problem?