Mailbox Index state "Failed"

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?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MASEE Solution Guide - Technical Dept HeadCommented:
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

If that also doesnt help.
Rebuild the index

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sgleeAuthor Commented:
 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 HeadCommented:
Try one by one 1, 2, 3
I suggest you restart service "Microsoft Exchange Search Indexer" and check.
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

sgleeAuthor 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 HeadCommented:
-->Do I need to reboot the entire server?
Please be patient.
sgleeAuthor 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 EngineerCommented:
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.
sgleeAuthor Commented:
I had Microsoft Engineer kill the processor and start the service.
Now the condition is Healthy.
sgleeAuthor 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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.