question

MattPollock-7884 avatar image
1 Vote"
MattPollock-7884 asked DanielBradley-7505 edited

Exchange 2019 Search Issues

Hi,

I'm in the process of migrating my orgs email infrastructure from Exchange 2013 to Exchange 2019
All new Exchange servers are running 2019 CU6, the Outlook client is the latest Office 365 click to run version, latest updates applied.

I'm 600 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.

During my investigation I'm seeing that whilst in cached mode performing a search eventually times out with the "Something went wrong and your search couldn't be completed", "It looks like there is a problem with your network connection"
Clicking the "Let's look your computer instead" link will return results contained in the local .ost file, but only going back as far as 3 or 4 months ago.
Cached mode is set to have all mail downloaded it is worth noting.

Putting Outlook in Online mode instead of cached mode does not improve things, exactly the same results are experienced when searching.

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 CU6 I find that this issue still being apparent is really poor.

Thanks

Matt

office-outlook-itprooffice-exchange-server-connectivity
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Exchange 2019 CU8 got released today, give it a try, KB458885.
this included fix might do the trick?: - https://support.microsoft.com/en-us/help/4583542


0 Votes 0 ·

Hi! I found this resolves permanently now! It is a link to my blog where we found a permanent fix without having to migrate to a new DB or start the mailbox assistant.
https://ourcloudnetwork.com/permanently-resolve-big-funnel-indexing-issues-in-exchange-server-2019/

0 Votes 0 ·
Clinton-9202 avatar image
0 Votes"
Clinton-9202 answered

Has anyone found a resolution to this issue yet? We have the same problem:

After installing an earlier CU (CU6 perhaps), BigFunnel stopped 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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ChristianBistriceanu-2181 avatar image
0 Votes"
ChristianBistriceanu-2181 answered ChristianBistriceanu-2181 commented

I am about to open a ticket with MS support too about this very subject. We have recenlty migrated to E2019 CU6 at first and not had anyone reporting any issues. Personally though, I did noticed search problems thing during the testing phase but at the time some of the articles have suggested using Outlook in cache mode which returned more and better results. We only recenlty started to allow users to use Outlook in cache mode and plan to have everyone the same way so I did not thougut this will become a big problem. Of course, I have started to receive more and more complains from the users which are now are not able to find items in their mail and is affecting their day to day tasks.

We have upgraded the E19 servers to CU8 and I will be looking to upgrade to CU10 in the next few months but I would like to know if MS is actively working on a fix and it would be worth waiting for another release that will address these search issues. I did used the following command on some mailboxes : Start-MailboxAssistant -Identity <Mailboxid> -AssistantName BigfunnelRetryFeederTimeBasedAssistant which seems to have improved the experience for a few users but it is still not working as it should.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

The only viable solution that seems to work for most people is creating a new mailbox database and transferring all clients from old to new. This forces Exchange to re-index everything. A pain in the ass and incredibly time consuming...but it seems to work. Not sure if this will have to be repeated after CU's.

1 Vote 1 ·

Thanks @Masterchief07-3066 ....That will be a lot of work for us as we have a large number of databases and users and it may take weeks to complete. I would like to understand the main reason for such behaviour too and what other troubleshooting steps one can take in order to rebuild and fix the index at the mailbox level. I think MS dropped the ball here again and they need to be able to provide a more feasable solution.

0 Votes 0 ·
MarchStephen-2237 avatar image
0 Votes"
MarchStephen-2237 answered

I have the same issue on CU8, I have since upgraded to CU 9 and CU10 with no success.
Opened a (paid for )case with Microsoft support, spent a month trying lots of options with them with no success. Also unable to migrate any mailboxes to a new database because the search data is not up-to date, quiet ironic that a outdated search issues prevents you fixing a search issue.
Microsoft eventually closed the case saying at this stage they have no fix and I need to watch for future CU's when it "may" be addressed.
Very disapointed

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.