Users were complaining about incomplete searches, recent emails missing from the search.  The users are on a terminal server not using cached mode, so they are relying on the mail server index.

I saw that the content index state was failed.  I stopped the services, removed the index and allowed to rebuild.

The previous index was 3.7GB.  After two days the index is only 95MB and search results are only showing the last two days.

My DB size is 107GB so I'm expecting it to be al ot larger than that.

I have already restarted the search services.

Content Index State shows healthy.  Not sure where to go from here.

I'm using a single Exchange server 2013 with CU7.

• Edited by Dynamic Computer Thursday, February 05, 2015 5:57 PM

I was able to do steps up to step 7 which I cannot do because we are not using DAG.  Can you provide an alternate command to reseed?

1. the NIC properties. Disabled it and rebooted the servers in sequence.
2. Disabled indexing on the failing database using Set-MailboxDatabase -Identity "DB06" -IndexEnabled $false.
3. Stopped the Exchange search service & Host controller service.
4. Renamed the Catalog index folder.
5. Started the services again.
6. Enabled the indexing on the database using Set-MailboxDatabase -Identity "DB06" -IndexEnabled $True
7. Reseeded the Catalog using the cmdlet Update-MailboxDatabaseCopy -Identity DB06 \MBXServer -CatalogOnly

Hi ,

Just proceed up to step 6 and that is enough to reseed the catalog index for an standalone mailbox server.

Note : Step 3 ,4 and 5 are the steps which will update the catalog index for the standalone mailbox server.

Hi,

Please rebuild the content index for this database and then check application log to see if there is Event id 108, 109 and 110.

Events which should be generated when you rebuilt the index successfully:

Event 108 - Indexer is Enabled
Event 109 - Indexer has created a new search index and will perform a full crawl for mailbox database
Event 110 - Full Crawl is Completed Successfully

Best regards,

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

I did the steps in article and rebooted the server.  The search index seems to be now at the expected size.

I did not get to see the expected events in the event log since I started the process on Friday and did not check it until Monday.  The events had already been overwritten.

Hi,

Based on your description, the search index is now at the expected size.

What about the search result? Could you search items normally?

Best regards,

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

Hi,

I would like to check on the status of this problem. Is there any update on this issue?

Best regards,

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