Search function does not work after upgrade Exchange 2019

Michal-doubleM 1 Reputation point

Dear team,

Our customer is experience search result issues where no new mails are shown after CU12 upgrade. I've found article to fix indexing issue but still notindex items is not changed and only increasing day by day. I found many articles how to fix it but nothing help.

  1. Start-MailboxAssistant -Identity Administrator -AssistantName BigfunnelRetryFeederTimeBasedAssistant
  2. New-SettingOverride -Name “Big Funnel Permanent Retry” -Component “BigFunnel” -Section “BigFunnelFailedItemsQuerySettings” -Parameters @(“ExcludePermanentFailures=false”) -Reason “Re-Index Messages” -MinVersion “15.1118.7)” -MaxVersion “15.1118.7)”
  3. Migrate Administrator mailbox to another DB which take an ages and failed with error message "Error: MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 6/27/2022 11:48:15 PM." [PS] C:\Windows\system32>Get-MailboxStatistics Administrator | FL notindex BigFunnelNotIndexedSize : 69.71 MB (73,098,053 bytes)
    BigFunnelNotIndexedCount : 176

Both service Microsoft Exchange Search and Microsoft Exchange Search Host Controller are running and set to Auto, even I've restart services and entire server, nothing really help.

Would you suggest how to re-initiate indexing for new mails after CU12?

Thank you!
Regards, Michal.

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,322 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Amit Singh 4,846 Reputation points

    You could try to restart those two services, Microsoft Exchange search and Microsoft Exchange Search Host Controller service, then wait for some time and try again.
    In addition, If restarting the service still doesn't work, you can try to migrate users to another database.