Mailbox Index state "Failed"

sglee
sglee used Ask the Experts™
on
Mailbox PropertiesI had my exchange server2010/SBS2011 crashed and had to perform Repair to be able to mount the mailbox database and I noticed Mailbox Index state "Failed".
How do I change "Content index state" to Healthy?

Thanks.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
EE Solution Guide - Technical Dept Head
Most Valuable Expert 2017
Commented:
Hi Sglee,
Please try to restart service "Microsoft Exchange Search Indexer"
If the index state state changes to crawling please wait for it to complete.
Else please run this command to update the catalog
Update-MailboxDatabaseCopy "database1" -CatalogOnly

Open in new window

https://practical365.com/exchange-server/cannot-activate-database-copy-content-index-catalog-files-in-failed-state/

If that also doesnt help.
Rebuild the index
https://practical365.com/exchange-server/monitor-rebuilding-content-indexes-exchange-databases/

Author

Commented:
@MAS,
 
 Can I try all these:
1. restart service "Microsoft Exchange Search Indexer"
2. Update-MailboxDatabaseCopy "database1" -CatalogOnly
3. Rebuild the index

While mailbox database is mounted and users are using emails?
MASEE Solution Guide - Technical Dept Head
Most Valuable Expert 2017

Commented:
Try one by one 1, 2, 3
I suggest you restart service "Microsoft Exchange Search Indexer" and check.
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

Author

Commented:
Serach Indexer stuck at STOPPINGI restarted  "Microsoft Exchange Search Indexer" service in SERVICES.MSC.  But it got stuck in "Stopping" for 10 minutes now.
Do I need to reboot the entire server?
MASEE Solution Guide - Technical Dept Head
Most Valuable Expert 2017

Commented:
-->Do I need to reboot the entire server?
Please be patient.

Author

Commented:
"Please be patient." ---> No problem. I can wait. By the way, does this impact Exchange server operation all all? Would Outlook users feel any impact while this service is being stuck?
Hemil AquinoNetwork Security Engineer
Distinguished Expert 2018

Commented:
1. restart service "Microsoft Exchange Search"
2-  restart service "Microsoft Exchange Search host controller"
3. Update-MailboxDatabaseCopy "database1" -CatalogOnly
4. Rebuild the index
5 Wait for a little while until it gets healthy.

Author

Commented:
I had Microsoft Engineer kill the processor and start the service.
Now the condition is Healthy.

Author

Commented:
Exchange Service@Hemil
(1) "restart service "Microsoft Exchange Search" --> I think this did the job.
(2) restart service "Microsoft Exchange Search host controller" --> I do not see "Microsoft Exchange Search host controller" in my Services.msc. However I see "Microsoft Exchange Search Host". Is that the same thing?
(3) "Update-MailboxDatabaseCopy "database1" -CatalogOnly" --> When I run this command, I get the following error:
[PS] C:\Users\admin\Desktop>Update-MailboxDatabaseCopy "new_mailbox2" -CatalogOnly
Database "new_mailbox2\*" has only one copy. This task is supported only for databases that have more than one copy.
Fyi, this is the only exchange server in the organization.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial