Exchange 2019 BigFunnel Indexing and Search Stopped After CU6

Question

Exchange 2019 BigFunnel Indexing and Search Stopped After CU6

Clinton 1

In case I was posting in a Q&A that was not quite related, has anyone found a resolution to this issue yet?

After installing an earlier CU (CU6 we believe), BigFunnel stopped indexing on all mailboxes. Every search now only yields emails prior to the CU install date.

I've tried installing CU9 and CU10 and still broken.
I've tried migrating mailboxes to a new database but get an error that I can't migrate because BigFunnel indexing is out of sync or something like that, so a catch 22.
I've tried Start-MailboxAssistant -Identity user1 -AssistantName BigFunnelRetryFeederTimeBasedAssistant

Is there anything else we can try?

Kael Yao 37,751 Reputation points Moderator

2021-08-04T06:10:13.577+00:00

Hi @Clinton

To my knowledge, the only way to rebuild the index in Exchange 2019 is to move the mailboxes to another database as you mentioned in the post.

I've tried migrating mailboxes to a new database but get an error that I can't migrate because BigFunnel indexing is out of sync or something like that, so a catch 22.

Would you please post the whole error message or a screenshot of the error when you fail to move the mailboxes?

2 answers

Your answer

Kael Yao 37,751 Reputation points Moderator

2021-08-04T06:10:13.577+00:00

Hi @Clinton

To my knowledge, the only way to rebuild the index in Exchange 2019 is to move the mailboxes to another database as you mentioned in the post.

I've tried migrating mailboxes to a new database but get an error that I can't migrate because BigFunnel indexing is out of sync or something like that, so a catch 22.

Would you please post the whole error message or a screenshot of the error when you fail to move the mailboxes?

Answer 1

Clinton 1

I am hesitant to work on migrating databases since other users report this was not a proper fix for this particular issue (where all mailboxes cease indexing). Though this user is not specifically using OWA, my issue affects both Outlook online and OWA. Are you confident this is my only option?

See below screenshot from other user:

Kael Yao 37,751 Reputation points Moderator

2021-08-04T06:42:11.407+00:00

Hi,
Thanks for your update.

While, there are also several threads giving feedback that a mailbox move would fix this issue.
For your reference:
Microsoft Exchange 2019 search issues since CU8 and HAFNIUM patches
Exchange 2019 CU9 Search not working (clean install)
Exchange 2019 cu5 search not returning all results - a chunk of time is missing
(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 totally understand your concern as it would take much effort to move all mailboxes.
Would it possible to first move a single affected mailbox to a new database?
If it actually works for you, you may go on and move the left ones.

Besides, it seems there are some problems with mailbox migration.
Anyway I think you may need to fix it.
Clinton 1 Reputation point

2021-08-04T18:48:47.293+00:00

New-MoveRequest -Identity "user1@keyman .com" -TargetDatabase "DB02"

Get-MoveRequest | Get-MoveRequestStatistics
DisplayName StatusDetail TotalMailboxSize PercentComplete
User1 TransientFailureTarget 2.606 GB (2,798,189,987 bytes) 20

Trying migration job from EAC next.
Validating... Syncing...
Status: Failed
Data migrated: 24.19 MB ‎(25,362,898 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
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 8/4/2021 2:25:41 PM.

The migration user report says the following:
Transient error BigFunnelTransientException has occurred. The system will retry.

I do also get MSExchangeFastSearch - EventID 1010
An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.FaultException: error CS1548: Cryptographic failure while signing assembly 'c:\Windows\Temp\b1nrhjm0.uiz\Microsoft.Exchange.BigFunnelFlow.28.dll' -- 'Error signing assembly -- Unknown error (8013141c)'
Clinton 1 Reputation point

2021-08-04T18:51:08.3+00:00

FYI, Microsoft Exchange Search Host Controller is set to Automatic and is running.

Also, I found this in V15/Logging/BigFunnelRetryFeederTimeBasedAssistant20210804-1.log
Clinton 1 Reputation point

2021-08-05T06:09:02.197+00:00

What do you think of this solution? I have similar errors in EventViewer.
https://social.technet.microsoft.com/Forums/en-US/fbf7bcd5-2148-4db2-a596-706f70df334f/exchange-server-2019-cu3-time-out-for-test-thread?forum=Exch2019
Kael Yao 37,751 Reputation points Moderator

2021-08-05T06:12:41.64+00:00

Hi,
I was thinking and testing the same thing :)
Please have a check of the status of "Microsoft Exchange Search" and "Microsoft Exchange Search Host Controller" service.
If they are not running, start the services and set the startup type to Automatic.
If they are running, restart them and see if you can move the mailbox successfully.
Clinton 1 Reputation point

2021-08-05T18:40:38.303+00:00

I've restarted those running services and it behaves the same.
Clinton 1 Reputation point

2021-08-07T20:35:41.29+00:00

I am going to copy this VM Exchange server into a lab environment, so if you have any aggressive suggestions, I wouldn't mind trying.. at least for testing purposes.
Kael Yao 37,751 Reputation points Moderator

2021-08-10T08:59:48.517+00:00

Hi,
Thanks for the effort!

Usually keeping the services in a running status and set them to run Automatically would get rid of this issue.
Just in case, did you resume the move request or create a new one after restarting the services?
Clinton 1 Reputation point

2021-08-12T02:05:04.577+00:00

Both.
Kael Yao 37,751 Reputation points Moderator

2021-08-16T09:00:04.873+00:00
Hi,
Please run a Test-ExchangeSearch on the mailbox and see if i would return some detailed error message:

Test-ExchangeSearch -identity <mailbox> -Verbose
Clinton 1 Reputation point

2021-08-18T09:09:29.777+00:00

There is no error message returned. Also, keep in mind that every single mailbox no longer indexes any mail ever since like CU6 or something. The CU broke BigFunnel feature on the server. Doesn't matter if you create an new Database. I've only seen a handful of people complain about this same issue. Lucky me!

Answer 2

Amit Singh 5,306

I have also face same problem and adde my experince in this blog - How to Fix Big Funnel Indexing Issues in Exchange 2019

Share via

Exchange 2019 BigFunnel Indexing and Search Stopped After CU6

2 answers

Your answer