Exchange 2019 Standart Edition Search problem

Question

Exchange 2019 Standart Edition Search problem

msbayazit 1

Hi everyone, I have an Exchange 2019 Server Standart edition on my environment. Two weeks ago i installed CU9 to exchange server. After this Cumulative Update i could not search any item on my or users mailboxes. I tried on owa or outlook client but there is no change. Also in exchange administrative events there is some events about this issue like event id 1010 source MSExchangeFastSearch. I googled it for some time but unfortunately could'nt find any solution. ![82826-event-id-1010.jpg][1] ![82776-search1.jpg][2] [1]: /api/attachments/82826-event-id-1010.jpg?platform=QnA [2]: /api/attachments/82776-search1.jpg?platform=QnA Please advice Thanks,

2 answers

Your answer

Answer 1

Yuki Sun-MSFT 41,381 Moderator

Hi @msbayazit ,

I tried on owa or outlook client but there is no change.

Have you tried switching between Exchange cached mode and Online mode in Outlook client and see if there would be any difference?
Is this issue now affecting all users in your environment?

Please try restarting the Microsoft Exchange Search service(MSExchangeFastSearch) on the sever and see how it goes.

Besides, it's suggested to try moving one of the affected user's mailboxes to a different mailbox database or a new created mailbox database to check the result.

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.

msbayazit 1 Reputation point

2021-03-31T12:12:32.983+00:00

Yes, i tried switching between cached mode and online mode in outlook clients and yes this is affecting all users.
I restarted the services and tried to migrate user mailboxes one database to another before but no change. Also migration was failed due to search problems. I don't know but In my research about this problem one of the given solutions mentions unlimited mailboxes may causing this. so far none of the solutions working.
Yuki Sun-MSFT 41,381 Reputation points Moderator

2021-04-02T05:15:31.777+00:00

Hi @msbayazit ,

I managed to build a test environment with Exchange 2019 CU 9, but cannot reproduce the issue as you described. Search works fine in both OWA and the Outlook client(Outlook 2019) on my end. So I think it's likely that the issue you encounted is not due to the Cumulative Update you have just installed.

Also migration was failed due to search problems. I don't know but In my research about this problem one of the given solutions mentions unlimited mailboxes may causing this.

Could you remove any perosnal information and share the error message when migrating a mailbox so that we can help do further research on this?
As regards to the possible causes related to "unlimited mailboxes", so have you had a chance to verify if this is the case on your end?

In addition, please check if Search folder and Advanced Find feature can work as expected in Outlook.

Answer 2

msbayazit 1

Hi @Yuki Sun-MSFT

first of all thanks for your assistance. Last weekend when i had more time to study on exchange server checked your suggestions. Unfortunately both of them didn't work.
Below you can find the error about migrating mailbox.

Error 1 :

3/29/2021 3:32:27 PM [EXCH] Connected to source mailbox '0710c9d9-503a-43ca-8784-98e662ff254b (Primary)', database 'Merkez', Mailbox server 'EXCH.contoso.com' Version 15.2 (Build 858.0).
3/29/2021 3:32:27 PM [EXCH] Request processing continued, stage LoadingMessages.
3/29/2021 3:32:27 PM [EXCH] Stage: LoadingMessages. Percent complete: 20.
3/29/2021 3:32:27 PM [EXCH] Stage: LoadingMessages. Percent complete: 20.
3/29/2021 3:32:27 PM [EXCH] Transient error BigFunnelTransientException has occurred. The system will retry (2/720).

Error 2:
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

Yuki Sun-MSFT 41,381 Reputation points Moderator

2021-04-06T07:00:24.64+00:00
Hi @msbayazit ,

Please check the Microsoft Exchange Search Host Controller service and see if it can be helpeful:

Open services.msc, find the Microsoft Exchange Search Host Controller service.

Right click it, choose Properties, set the Startup type to "Automatic", restarting the service and check the result.

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.
Yuki Sun-MSFT 41,381 Reputation points Moderator

2021-04-09T05:27:57.137+00:00

Hi @msbayazit ,

Just checking in to see if you have had a chance to check the Microsoft Exchange Search Host Controller service. Feel free to post back if there is any update or should you would like further assistance on this issue.

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.
Nico 1 Reputation point

2021-04-28T07:05:54.4+00:00

I'm facing similar problems with no search results or old search results.

Just started the Service Microsoft Exchange Search Host Controller and restarted the service Microsoft Exchange Search.

When will there be results to check? How long does it take for the server to re-index and provide better search results?

In my case the Microsoft Exchange Search Host Controller was deactivated. Is this service needed to provide search results? I don't know why it's deactivated.
Nader Hussein 1 Reputation point

2021-08-14T06:27:03.797+00:00

HI @msbayazit I have the same problem

Error: MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service

Transient error BigFunnelTransientException has occurred

Did you figure out the problem?

Share via

Exchange 2019 Standart Edition Search problem

2 answers

Your answer