Microsoft Exchange 2019 search issues since CU8 and HAFNIUM patches

Phil Tyler 101 Reputation points

We have on-premises Exchange 2019 which was at CU6. When then HAFNIUM news broke I immediately updated to CU 8 and then installed the HAFNIUM patches overnight. The upgrade appeared to go well and after a bit of fiddling with IIS to get OWA and Exchange Admin working again all appeared normal.

Since then though users have been reporting that Outlook 2019 searches on their desktop PCs are NOT returning all results, specifically nothing after the date of the patch (3rd March 2021). Also when you sign in remotely using OWA the same thing is happening. No recent emails are returned by a search.

I have an email from a colleague dated yesterday with the subject line being about their birthday. If I put 'birthday' as the search term nothing is returned when restricting the search to 'within the last week' on OWA, yet I can clearly see & open the email in the Inbox view. If I don't restrict the date only old emails from January this year and earlier are returned.

The same happens in Outlook 2019, the first search result returned is the same as the one in OWA from January.

If you use the Advanced Search function then the email from yesterday IS found!!

If you use Apple Mail on an iPhone linked to the Exchange server then the email is found during a search.

I've rebuilt the Windows Search index on Windows 10 (all the desktop PCs are on Windows 10) and this hasn't worked, even though it took hours to re-index Outlook. Checking the Indexing Status in Outlook 2019 shows zero items still to be indexed.

I've tried turning off cached Exchange Mode and turning it back on again. It was the same with the cache on as well as off.

My last ditch try is turning the cache off, deleting the OST file, then turning it back on. This will force Outlook 2019 to re-download all the email from the server. I presume the local Windows Search only indexes the OST file so if that's corrupt it will miss items out. I'm not hopeful that this will work as the search doesn't work in OWA and that has NOTHING to do with desktop Outlook and it's local OST cache file.

Anyone else got any other ideas?

Would a repair of the Exchange database work? How dangerous is that? Is it worth trying Isinteg ?

Outlook Management
Outlook Management
Outlook: A family of Microsoft email and calendar products.Management: The act or process of organizing, handling, directing or controlling something.
5,004 questions
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,440 questions
{count} votes

Accepted answer
  1. Phil Tyler 101 Reputation points

    I created a new temporary database and moved some of the mailboxes over and that fixed the problem for those mailboxes. So over the weekend I moved all the rest and then moved them back before deleting the temporary database.

    Thanks AndyDavid for the suggestion!

    Moving the mailbox must force a rebuild of the index. One of the major changes in Exchange 2019 from 2016 is that the index is now inside the database and is maintained by Bing technology known as BigFunnel. The vast majority of blog posts and tech forums posts about how to re-index an Exchange database are for 2016 and earlier. In most cases a fix from Exchange 2016 will work on 2019 but not in this case!

    To find out which mailboxes have unindexed items, and how many, you can run this from the Exchange Management Shell...

    Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | ? {$_.BigfunnelNotIndexedCount -ge "1"} | ft DisplayName,BigfunnelNotIndexedCount

    Obviously the "Microsoft Exchange Search Host Controller Service" and the "Microsoft Exchange Search" must be running and set to Automatic as they maintain the index.

    1 person found this answer helpful.

3 additional answers

Sort by: Most helpful
  1. Yuki Sun-MSFT 40,916 Reputation points

    Hi @Phil Tyler ,

    Is there any relevant event logs recorded in the Event Viewer on the server?

    Please have a check and make sure the services below are running properly on the Exchange 2019 CU8 servers and the startup type is "automatic":

    • Microsoft Exchange Search Host Controller Service
    • Microsoft Exchange Search

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Lalenko Igor 1 Reputation point

    For me, the box migration solution was not applicable, so I found another way.

    Start EMS from Admin

    Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

    Start-MailboxAssistant -Identity admin@Company portal .com -AssistantName BigFunnelRetryFeederTimeBasedAssistant

    Or a loop for OU. But reindexing is slow. 4TB of boxes re-indexed 2 weeks

    $name = Get-Mailbox -OrganizationalUnit Users
    foreach ($names in $name)
    Start-MailboxAssistant -Identity $names -AssistantName BigFunnelRetryFeederTimeBasedAssistant

    Tracking reindexing

    Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | ? {$_.BigfunnelNotIndexedCount -ge "1"} | Start-MailboxAssistant -AssistantName BigFunnelRetryFeederTimeBasedAssistant

    0 comments No comments

  3. Brendan Tween 1 Reputation point

    I am facing the same problem in a 2013/2019 hybrid environment and I am sort of at a loss... How is it possible that MS pivoted search to Bing/mailbox index and now you only have one opportunity to index a mailbox - if for some reason that doesn't work, you are out of luck and have to move the mailbox???

    This is beyond ridiculous. Why is Bing not persistently crawling mailboxes as part of db maintenance?

    It makes no sense to me. I am supposed to move 1000 mailboxes to a temp db? We will need to hire someone specifically for that job.

    What is MS going to do about this? This is not a small problem...