Search bug with Exchange 2019

mark3grahams 36 Reputation points
2020-08-12T00:35:48.737+00:00

Continuation of archived forum question search-bug-with-exchange-2019

This is now being pushed into CU8 (maybe).

I also received this info from an engineer.
"When testing this issue out, for some reason it only appears to affect “S” and the few other letters that I have tried doesn’t appears to have the same issue. Which is good that doesn’t affect many different scenarios.

It appears that just the “S” at the start of the search query follow by numbers has this issue occur.

When testing out the other letters or different combination of numbers it works. You should also be able to find the message without including the letter “S”."

Exchange | Exchange Server | Management
{count} votes

7 answers

Sort by: Most helpful
  1. mark3grahams 36 Reputation points
    2020-12-02T14:12:42.337+00:00

    Latest

    "I just wanted to provide an update that I have synced with PG and provided what I think is a possible code fix. However, they are still going to need to review and investigate it as we don’t want to have a regression within the search functionality. This process can take some time now for them to review and determine how to proceed next. I will let you know if there are any changes."

    2 people found this answer helpful.
    0 comments No comments

  2. mark3grahams 36 Reputation points
    2020-12-07T18:05:26.207+00:00

    "I just wanted to provide an update to you regarding this issue. It looks like we have a fix and is expected to be in Exchange 2019 CU9 release that is coming in March."

    "Since it is early, I would say that it is close to locked in. But there is a chance that it could be pulled for some other issue that is found later down the road in BETA testing. I am in the process of testing out the changes myself to make sure that it is fixed as how we would expect it to be fixed."

    2 people found this answer helpful.

  3. mark3grahams 36 Reputation points
    2020-11-23T19:39:34.23+00:00

    Here is the latest follow up.

    "I am still working with the product group on this issue. I am working updating some internal content and sync with PG on this here either today or tomorrow. I will still continue to dig into this issue, however, I have found that Q and L also have the same outcome as S. Hopefully we can determine a way to fix the issue, however, right now it looks like it caused by our word breaker code that causes the new big funnel feature to not work as intended. If it turns out to be in the word breaker, it is going to be harder to provide a fix for this."

    1 person found this answer helpful.

  4. Edward van Biljon 6 Reputation points Volunteer Moderator
    2020-08-12T05:27:18.88+00:00

    Hi

    If it is a bug in Exchange 2019, please log it with Microsoft.

    0 comments No comments

  5. Eric Yin-MSFT 4,396 Reputation points
    2020-08-12T06:13:07.96+00:00

    Do you have any policy or restriction that not allowing you to use Exchange cached mode? You can use Exchange cached mode as a workround.
    Then just wait for Microsoft updates, it seeems CU5 has fixed some search issues, there should be some engineer working on it.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.