This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 60%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello. Exchange 2019. On-premise. After the crash, mailboxes were restored via Veeam. Users started complaining that the search was not working properly.
PS C:\Users\user> Get-MailboxStatistics ******@domain.ru | fl BigFunnelCorruptedCount
BigFunnelCorruptedCount: 151625
After moving the box to a different base, the search works fine.
PS C:\Users\user> Get-MailboxStatistics ******@domain.ru | fl BigFunnelCorruptedCount
BigFunnelCorruptedCount: 0
https://support.microsoft.com/en-us/topic/incomplete-search-results-after-installing-an-exchange-server-2019-update-96ae2ef0-4569-4327-8d0c-8a3c1abdc1f6 I found this article, ran the commands:
New-SettingOverride -Name "Big Funnel Permanent Retry" -Component "BigFunnel" -Section "BigFunnelFailedItemsQuerySettings" -Parameters @("ExcludePermanentFailures=false") -Reason "Re-Index Messages"
Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
Start-MailboxAssistant -Identity "user" -AssistantName BigFunnelRetryFeederTimeBasedAssistant
But the indexing is not done.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 59%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Hello Андрей Михалевский
Normally you just need to move it to another database.
Did any errors occur when you ran the above command? Just noticed something different, are you missing the Build Number part?
Regards SF
I have 1,500 boxes. I can't move each one. No errors. These parameters are not required And I don't understand what a max version and a min version are. There is no description of how to find your parameters
You could check the description of the max and min versions in this article.
https://learn.microsoft.com/en-us/powershell/module/exchange/new-settingoverride?view=exchange-ps#-maxversion
This is a query regarding Exchange 2016 and 2019.
https://learn.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019#exchange-server-2019
The default value is blank ($null), which means the override applies to all versions of Exchange 2016. Or i need min 15.2.196.0 and max 15.02.1258.028 ?
Hello Андрей Михалевский
Please review the three methods listed under this section.
Also I searched a lot and it seems that migrating to a new database is the only effective way, albeit time consuming. If you are concerned, you may consider migrating during off-hours. https://www.reddit.com/r/exchangeserver/comments/wpfq14/big_funnel_indexing_workaround_on_exchange_2019/
Kind Regards
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
I wanted to check in and thank you for your time and patience throughout this issue.
---If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.