Comments on: Rebuilding Content Indexes for Exchange Databases

By: Sukanta

Sukanta — Mon, 14 Nov 2022 06:07:45 +0000

I have exchange 2016 standalone server with one database of 1 TB. Context index is keep failing even after stop service and delete and start the service..its keep failing. To reduce the load have created a new database and try to move to mailbox ( 1gb -very small )to another database of same server, migration is failing after 5-10% with error stalled due to target index . Even if we disabled indexing both source and target still we are not able to move mailbox between 2 database.

So neither we are able to make the contex index of primary database health nor we move mailboz between 2 database

By: Hannes Louwrens

Hannes Louwrens — Mon, 24 Jan 2022 13:29:32 +0000

Would this be the same for Exchange 2019?

As I do not see the GUID folder under my DB directory…

By: haiqing ma

haiqing ma — Sat, 07 Nov 2020 09:42:36 +0000

Great Article..

By: JimBob

JimBob — Sat, 16 Feb 2019 17:25:52 +0000

In reply to ptbNO. I did all this several times and it never recreates the deleted folder (stop.start services, reboot whatever) and the state is Healthy. OWA search still fails.

By: ptbNO

ptbNO — Mon, 11 Feb 2019 11:16:10 +0000

In reply to ptbNO. not sure how active this blog is, but will leave another brief update in case anyone feel like replying: So it's been 1 week, and the last database still has status crawling. So something must for sure be stuck.

By: ptbNO

ptbNO — Tue, 05 Feb 2019 09:42:19 +0000

In reply to ptbNO. Second database still "Crawling". Been like 36 hours since Performance Monitor stopped counting down. I've read the content index rebuild can take a long time, and I wouldn't worry if PM was still counting down. But this long with same status, when PM seems to think the process is finished? Can't be normal?

By: ptbNO

ptbNO — Mon, 04 Feb 2019 15:02:41 +0000

Hi Paul/everyone,

single on-premises server, needed to rebuild Content Index on 2 of my databases and renamed/removed the GUID folders of the databases while opening performance monitor to follow progress:
Countdown in Performance monitor on first database finished, then for another 30 minutes or so afterwards ContentIndexStatus (when checking Get-MailboxDatabaseCopyStatus) was “Crawling” before it went to “Healthy”.

Took another 7 hours before countdown in Performance Monitor on second database finished. However, status on this particular database is still “Crawling”, and it’s now like 16 hours since countdown in Performance monitor was done. Is this normal, or is something stuck? As far as I know there is no other way than what I’ve been doing to track progress?

By: StanG

StanG — Thu, 17 Jan 2019 14:52:40 +0000

In reply to boe.

By default it’s showing CPU % counter. You can uncheck that one.

You need to right click on performance counter in tree on the left, and select properties.
Then on the DATA tab you need to add Counters, scroll down in the list of counters until you see “MSEXchange Search Indexes”, under that category you select “Crawler: Mailboxes remaining”. Below that in instances, you select all the databases individually instead of total.
That’s it.
You can still adjust the scale of the graph in properties, of switch between different graph styles.

By: boe

boe — Thu, 27 Sep 2018 04:32:24 +0000

How do you get that database index to show up in the performance monitor? I open performance monitor and it show s last, average minimum – no idea what it is trying to tell me but it doesn’t look like yours

By: Dave

Dave — Mon, 30 Jul 2018 17:27:37 +0000

Paul, could you post the procedure for deleting the corrupt index files and rebuilding them for DAG members?