asked on Exchange search broken. Client search results don't return any hits after March of this year.
Exchange 2019 (15.2)
Indexing is running.
Running a test search on a sample mailbox indicates search shows no output whatsoever.
And the search index status also seems to show that it isn't doing anything.
Get-MailboxDatabaseCopyStatus | fl Name,*index*
Here is what I tried:
Remove all four directories that are located under the following folder: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data\Nodes\Fsis
Indexing is running.
Get-MailboxDatabase | Format-Table Name,IndexEnabled
Running a test search on a sample mailbox indicates search shows no output whatsoever.
Test-ExchangeSearch -Identity sample@domain
And the search index status also seems to show that it isn't doing anything.
Get-MailboxDatabaseCopyStatus | fl Name,*index*
Creating a new session for implicit remoting of "Get-MailboxDatabaseCopyStatus" command...
Name : db01\EXCHANGE
ContentIndexState : NotApplicable
ContentIndexErrorMessage :
ContentIndexErrorCode :
ContentIndexVersion :
ContentIndexCrawlVersion :
ContentIndexBacklog :
ContentIndexRetryQueueSize :
ContentIndexMailboxesToCrawl :
ContentIndexSeedingPercent :
ContentIndexSeedingSource :
ContentIndexServerSource :
Here is what I tried:
stop-service msexchangefastsearch
stop-service hostcontrollerservice
Remove all four directories that are located under the following folder: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data\Nodes\Fsis
cd C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer
.\installconfig.ps1 -action I -datafolder "c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
stop-service msexchangehm*
Get-Mailbox -Monitoring | Remove-Mailbox
start-service msexchangehm*
start-service msexchangefastsearch
start-service hostcontrollerservice
Exchange
Last Comment
Ted Fines
ASKER
Thank you Saif Shaikh. Good to know about that change in 2019.
But Search doesn't work at all. Search is broken. How do I fix search in Exchange 2019?
But Search doesn't work at all. Search is broken. How do I fix search in Exchange 2019?
ASKER
I found this command to show how many unindexed messages mailboxes have:
All of the mailboxes have heaps of unindexed messages.
Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | ? {$_.BigfunnelNotIndexedCount -ge "1"} | ft DisplayName,BigfunnelNotIndexedCount
All of the mailboxes have heaps of unindexed messages.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you. The Mailbox Assistant command ran but didn't work. I tried it for a few mailboxes. The unindexed message count doesn't decrease.
I created a new database and moved users over to it. Search works again. Thanks for your help.
I guess I'll just migrate to a new database every time I need to repair a search index. This is their flagship "Enterprise" product. Right.
I created a new database and moved users over to it. Search works again. Thanks for your help.
I guess I'll just migrate to a new database every time I need to repair a search index. This is their flagship "Enterprise" product. Right.
The search infrastructure is rebuilt in Exchange 2019 and this is by design.
Exchange 2019 uses the new search engine called "Big Funnel", using Bing technology to make the search even faster and provide better results. Search indexes are not longer stored on disk per Mailbox database, but search indexes are now stored inside the Mailbox database on a per Mailbox basis. So the context index for the database shows NotApplicable in Exchange 2019, and the unhealthy index state will become a thing of the past.
For reference: EXCHANGE 2019 RELEASED AND AVAILABLE ON MICROSOFT VOLUME LICENSE CENTER
Reference Articles:
https://social.technet.microsoft.com/Forums/en-US/2516a8df-db14-493d-a989-f59e8a3b647e/content-index-state-for-database?forum=Exch2019
https://www.reddit.com/r/exchangeserver/comments/ei5hql/search_indexing_showing_as_na_exchange_2019/
The change is due them moving the Content Index State from being a Database level feature (where it has to be in sync as part of a DAG), to being at the mailbox level.
https://www.codetwo.com/admins-blog/whats-new-in-exchange-2019/#search