Forum Discussion
(Outlook) Search issue after upgrade to build 15831.20190
I've experienced the same issue where the mailbox indexing stops working after upgrading to EX2019 CU12.
What solved it in my case is to run this command on a regular basis:
Start-MailboxAssistant -Identity <mailbox ID> -AssistantName BigFunnelRetryFeederTimeBasedAssistant
This command needs to be run on the Exchange Server itself.
You can run the following commands before and after the above command to verify it did indeed do something:
Get-MailboxStatistics <mailbox ID> | fl *NotIndex*
This will output the 'BigFunnelNotIndexedSize' and 'BigFunnelNotIndexedCount'.
Just run it before and after to compare the numbers, they should be decreasing. However, the numbers most often don't go all the way down to 0. Why is explained in the second bullet point below.
There's still a couple of problems I'm dealing with:
- I have not found an option yet to run the command against the entire mailbox db.
- It will not re-index emails that have not been indexed for too long. I'm not sure what the timeframe is, but at one point the emails that are not indexed, will go into a failure state. Those ones will not be re-indexed with above command and I have yet to find a way to do so.
Hope this helps a little.
*EDIT*
I just found the solution for my second bullet point about not all emails being re-indexed:
https://support.microsoft.com/en-us/topic/incomplete-search-results-after-installing-an-exchange-server-2019-update-96ae2ef0-4569-4327-8d0c-8a3c1abdc1f6
- Thank you for this solution. Unfortunately, the Exchange server is managed by a third company so I can't run these commands. I'll let them know.
- Hi,
We have the same issue in our infrastructure.
After Office 365 has been updated to 2211 Build 16.0.15831.20220, the search feature on Outook is not working anymore when it had to search on the server.
It was working fine in 2210 version.
The problem is not on the server side, as it was working fine in Outlook 2210 version and the search is working fine when using webmail.
Do we have to switch to the enterprise annual channel for Office updates ?
This is clearly a recurrent problem with Outlook.
