Exchange 2019 Search Issues

%3CLINGO-SUB%20id%3D%22lingo-sub-1907683%22%20slang%3D%22en-US%22%3EExchange%202019%20Search%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1907683%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERecently%20in%20the%20organization%2C%20we%20performed%20the%20migrating%20email%20infrastructure%20from%20Exchange%202016%20to%20Exchange%202019%3CBR%20%2F%3EAll%20new%20Exchange%20servers%20are%20running%202019%20CU7%2C%20the%20Outlook%20client%20is%20the%20Office%202019%20with%20latest%20updates%20applied.%3C%2FP%3E%3CP%3E%3CSPAN%3EI'm%20400%20mailboxes%20into%20the%20migration%2C%20and%20I'm%20starting%20to%20get%20users%20complaining%20about%20being%20unable%20to%20search%20Outlook.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3EAll%20of%20the%20Outlook%20clients%20are%20in%20cached%20mode%20by%20default.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EAfter%20reading%20a%20few%20threads%20I%20have%20restarted%20the%20following%20services%20on%20all%20new%20mailbox%20servers%20%22Microsoft%20Exchange%20Search%22%2C%20MIcrosoft%20Exchange%20Search%20Host%20Controller%22%20with%20the%20hop%20that%20the%20database%20search%20indexes%20will%20be%20refreshed%2Frebuilt.%20I%20did%20this%20yesterday%20and%20left%20the%20servers%20overnight%2C%20but%20there%20is%20no%20improvement%20in%20searching%20in%20my%20testing.%3C%2FP%3E%3CP%3EHas%20anyone%20had%20simliar%20experiences%20with%20their%20setup%2C%20and%20more%20importantly%20being%20able%20to%20fix%20these%20issues%3F%3CBR%20%2F%3EConsidering%20Exchange%202019%20is%20now%20on%20CU7%20I%20find%20that%20this%20issue%20still%20being%20apparent%20is%20really%20poor.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Eemsantos%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1907683%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1955933%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202019%20Search%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1955933%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F875021%22%20target%3D%22_blank%22%3E%40emsantos%3C%2FA%3E%26nbsp%3BHello!%20I%20also%20have%20this%20problem!%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20both%20problem%20in%20cashed%20and%20in%20online%20mode%20for%20some%20reason.%3C%2FP%3E%3CP%3EDid%20u%20get%20a%20solution%20for%20this%3F%3C%2FP%3E%3CP%3Ei%20have%20problem%20finding%20emails%20after%202019%20when%20searching.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1958772%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%202019%20Search%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1958772%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F875021%22%20target%3D%22_blank%22%3E%40emsantos%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%3C%2FP%3E%3CP%3EYou%20can%20follow%20this%20post%20if%20the%20users%20who%20have%20the%20problem%20are%20located%20in%20Exchange%202019%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftkolber.medium.com%2Ffixing-search-indexing-issues-within-exchange-2019-mailboxes-eba04d207312%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftkolber.medium.com%2Ffixing-search-indexing-issues-within-exchange-2019-mailboxes-eba04d207312%3C%2FA%3E%3C%2FP%3E%3CP%3Ein%20short%2C%20try%20to%20move%20the%20users%20to%20another%20database%20or%20if%20the%20command%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStart-MailboxAssistant%20-Identity%20%3CMAILBOX%20id%3D%22%22%3E%20-AssistantName%20BigfunnelRetryFeederTimeBasedAssistant%26nbsp%3B%3C%2FMAILBOX%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20the%20users%20on%20Exchange%202016%20having%20this%20issue%2C%20you%20will%20need%20to%20confirm%20that%20Content%20Indexing%20on%20the%20database%20Level%20and%20ensure%20that%20it's%20healthy.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fpractical365.com%2Fexchange-server%2Fexchange-2016-failed-content-index%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpractical365.com%2Fexchange-server%2Fexchange-2016-failed-content-index%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi,

 

Recently in the organization, we performed the migrating email infrastructure from Exchange 2016 to Exchange 2019
All new Exchange servers are running 2019 CU7, the Outlook client is the Office 2019 with latest updates applied.

I'm 400 mailboxes into the migration, and I'm starting to get users complaining about being unable to search Outlook.
All of the Outlook clients are in cached mode by default.

After reading a few threads I have restarted the following services on all new mailbox servers "Microsoft Exchange Search", MIcrosoft Exchange Search Host Controller" with the hop that the database search indexes will be refreshed/rebuilt. I did this yesterday and left the servers overnight, but there is no improvement in searching in my testing.

Has anyone had simliar experiences with their setup, and more importantly being able to fix these issues?
Considering Exchange 2019 is now on CU7 I find that this issue still being apparent is really poor.

 

Thanks,

 

emsantos

5 Replies

@emsantos Hello! I also have this problem! 

I have both problem in cashed and in online mode for some reason.

Did u get a solution for this?

i have problem finding emails after 2019 when searching.

@emsantos 

Hi

You can follow this post if the users who have the problem are located in Exchange 2019

https://tkolber.medium.com/fixing-search-indexing-issues-within-exchange-2019-mailboxes-eba04d207312

in short, try to move the users to another database or if the command 

 

Start-MailboxAssistant -Identity <Mailbox id> -AssistantName BigfunnelRetryFeederTimeBasedAssistant 

 

If the users on Exchange 2016 having this issue, you will need to confirm that Content Indexing on the database Level and ensure that it's healthy.

https://practical365.com/exchange-server/exchange-2016-failed-content-index/

 

 

 

There is no Start-MailboxAssistant, not on Exchange 2019 CU8 at least. Anyone else successfully ran this command?

If you run this command first, Start-MailboxAssistant becomes available: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.SnapIn

However, it won't help since the specific assistant, BigfunnelRetryFeederTimeBasedAssistant, does not seem to exist, at least not on Exchange 2019 CU9. If anyone has any information about how to restart indexing of Exchange 2019 mailboxes, without moving them to another database, I would be very grateful.

@Jan_BostromThe assistant exists (also in CU8), but it seems to be case-sensitive for me, so if I use

 

BigFunnelRetryFeederTimeBasedAssistant

 

(capital F in BigFunnel), it works for me. Let me know if it works for you.