none
Search bug with Exchange 2019 RRS feed

  • Question

  • Hi there we have a bug with Outlook 2016 and Exchange 2019.

    The bug is to do with the way search works when Cached mode is OFF.

    An Email has the subject "S150757"

    When searching for "S150757" I get no results BUT when I search for "s150757" I do get the expected results...

    Other mentions of the bug here:

    https://www.reddit.com/r/exchangeserver/comments/c5dt8e/exchange_2019_search_behavior/

    Monday, July 1, 2019 8:25 AM

All replies

  • This bug only occurs when cached mode is OFF... it works fine when cached mode is on.
    Monday, July 1, 2019 3:05 PM
  • Searches work fine through OWA...
    Monday, July 1, 2019 8:36 PM
  • Hi liltbrockie,

     

    What’s your Exchange 2019 and Outlook 2016 build numbers?

     

    With my research, Microsoft not released related known issue on Exchange 2019 yet. I also tested in my Exchange 2019 RTM+ Outlook 2016(16.0.4266.1001) Lab, the search feature works as normal.

     


     

    If there is only one user facing this issue, I suspect this issue is due to an interrupted Outlook profile or Office installation. Please try to re-create an Outlook profile for this user or perform a repair with Office. Then check if this issue persists:

     

    Create an Outlook profile

    https://support.office.com/en-us/article/create-an-outlook-profile-f544c1ba-3352-4b3b-be0b-8d42a540459d

     

    To exclude the client side impact, please install the Outlook client in another clean Windows PC, then check the result.

     

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, July 2, 2019 5:08 AM
  • Hello Kelvin! 


    Thanks for replying!

    Outlook Build is 16.0.4849.1000 32 bit.

    Exchange Build is 15.2 (Build 330.5)


    So the way you did the search was not as I described... You searched for "s150757", my search fails when I search for "S150757"


    Allow me to describe in more detail my steps to recreate...


    Make sure that cached mode is off.

    Remove Outlook from the list of included indexing locations.

    Restart Outlook and perform the search "s150757"

    You will see results as expected.

    Perform the search again but with "S150757"

    You will see no results returned .. this is not expected.

    You can see some images related to the bug here:

    https://imgur.com/a/jQLjbp7

    Tuesday, July 2, 2019 6:50 AM
  • I notice that there is a CU2 update for exchange. I guess I will try and install, however there is nothing in the CU2 update release notes to suggest this bug has been fixed.
    Tuesday, July 2, 2019 7:41 AM
  • Hi liltbrockie

     

    Thanks for your reply, I tested it again and attached a new screenshot in my last reply.

     

    I understand that your current Exchange 2019 version is CU1, since my Exchange 2019 Lab is RTM. If you have tried all methods in my last reply, and the issue still occurs, I suggest you update the Exchange server and Outlook client to the latest build.

     

    To get Cumulative Update 2 for Exchange Server 2019, please go to Microsoft Volume Licensing Center.

     

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Tuesday, July 2, 2019 8:56 AM
  • Hi liltbrockie,

     

    I am writing here to confirm with you how the thing going now?

     

    If you need further help, please provide more detailed information, so that we can give more appropriate suggestions

     

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 5, 2019 7:56 AM
  • Hi Kelvin.... I am due to update Exchange Server tonight... will let you know...
    Monday, July 8, 2019 8:43 AM
  • Hi Kelvin.. updated to CU2 and search bug persists.. acting just the same way as it was before...
    Monday, July 8, 2019 5:40 PM
  • Here is a video showing the bug in action:

    https://www.youtube.com/watch?v=exuIOqYD8zM&feature=youtu.be

    Tuesday, July 9, 2019 7:50 AM
  • Hi liltbrockie,

     

    The mailbox move reindexes the items in the mailbox. Please create a new mailbox database in the Exchange 2019 server, then move the affected mailbox to the new database, then check the index issue disappears or not.

     

    Regards,
    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 12, 2019 9:56 AM
  • There is a problem with a Exchange 2019 and Outlook 2016 search, for example, one user have Outlook 2016 with primary and archive mailbox - search is working. Another user, the same databases, have Outlook 2016 with primary and archive mailbox - search is working partialy, it search within archive part, but not search within primary mailbox, in both cases cached mode disabled.

    For example, when opening second mailbox with Outlook 2010, search is working correctly...

    In Exchange 2016 and earlier there was option to delete index files, and restart search services.

    In exchange 2019, move mailbox to different database is FAR FROM OPTIMAL, imagine, that you need to move somewhere every non working search mailbox. It will take unnecessary space, it will take your time, it will brake backup!

    Please implement some comand, that we can regenerate indexes at the mailbox level, or at least at database level in exchange 2019!!! 

    Also please implement, that users Archive is possible to hide from Outlook!!!



    Tuesday, July 16, 2019 11:24 AM
  • Not sure the above applies to me... my user has no archive mailbox
    Tuesday, July 16, 2019 11:40 AM
  • I found, what caused my Exchange2019+Outlook2016 primary mailbox search not working problem.

    That mailbox was recently migrated from Exchange 2016. And when i press Ctrl + Mouse Right to outlook icon - Connection Status, i found, that the line, that represented primary mailbox - connect to previous server (E2016) instead of E2019 (other lines connected to new server).

    So, i found this https://www.itjon.com/outlook-still-trying-to-connect-to-old-exchange-server-after-moving-to-office-365/

    added registry record:

    Add: ExcludeScpLookup=dword:1

    to
    HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
    (This is for Outlook 2010, Outlook 2013 and Outlook 2007 will be the different area such as xxx\15.0\xxxx)

    and, search started working within Outlook 2016!!!



    Wednesday, July 17, 2019 7:39 AM
  • OK thanks.. DisplayName but again.. your issue and fix does not apply to me...
    Wednesday, July 17, 2019 7:42 AM
  • Hi ,

     

    Have you tried the method of moving the mailbox to other database?

     

    If you need further help, please provide more detailed information, so that we can give more appropriate suggestions

     

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com


    Monday, July 22, 2019 8:23 AM
  • Hi Kevin,

    I just installed at a new client an fresh install of 2019. Imported all mailboxes from old Exchange 2010 by exporting/importing PST's.

    Here our results are also not OK, for example we see new search results (from today)

    And then very old results, we miss like 2016 - 2019 in the search results.

    In older exchange we did do a reset of search index by removing .Single folder. but in 2019 it's not there.
    It's a standalone Exchange server with 1 DB, no copy.

    I see in your replies here the Move request should fix this. Is there a better way? Otherwise I need to prepare new Database and move all mailboxes and then my VHD size is getting huge again. So it's quite timeconsuming.. Instead of what we had before.

    Monday, July 22, 2019 11:15 AM
  • Hi Kevin,

    I just installed at a new client an fresh install of 2019. Imported all mailboxes from old Exchange 2010 by exporting/importing PST's.

    Here our results are also not OK, for example we see new search results (from today)

    And then very old results, we miss like 2016 - 2019 in the search results.

    In older exchange we did do a reset of search index by removing .Single folder. but in 2019 it's not there.
    It's a standalone Exchange server with 1 DB, no copy.

    I see in your replies here the Move request should fix this. Is there a better way? Otherwise I need to prepare new Database and move all mailboxes and then my VHD size is getting huge again. So it's quite timeconsuming.. Instead of what we had before.

    we have exactly the same Problem. imported pst files and search not working. ridiculous that there is no way to recreate Exchange search index. cant understand why they removed it in 2019...
    Monday, July 22, 2019 3:46 PM
  • Hi Kevin,

    Any update on this ?

    Wednesday, July 24, 2019 9:39 PM
  • Hi InfoCN,

    I did some further research I did;

    - Create new DB

    - Moved all boxes

    > Search was still not good

    I made a copy of the terminal server, installed office 2013 (Instead of 2016) > same issue

    I made another copy and installed office 2019 (Instead of 2016) > same issue

    in OWA (Webmail) I do not have the issue. There all is OK

    I upgraded Exchange 2019 to 2019 CU2 > Issue still there.

    So far I have no solution yet and my client has worse search results :s
    On holiday now, next step is create a new Windows 10 VM or so to test how it goes in there..

    Tuesday, July 30, 2019 9:51 PM
  • I too have created a new DB in order to fix this problem and it has NOT worked.
    Wednesday, July 31, 2019 2:38 PM
  • Hi,

    After my further research, since the complexity of the issue, and support resource limit in our forum, I suggest you refer to the following link and open a ticket, the engineers will provide professional support with you.

     

    https://support.microsoft.com/en-sg/hub/4343728/support-for-business

     

    Thanks for your patience and understanding.

     

    Regards,

    Kelvin Deng


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com


    Friday, August 2, 2019 9:40 AM
  • Do you have any update?

    I just tested on a new Windows 10 VM, same issue. even with Outlook 2010 tested.
    When I use other keywords the mails show up.

    It only affects "imported mails" - All new mails seem to correctly indexed and can be searched the right way!

    (I migrated with PST export - import)

    Sunday, August 11, 2019 10:33 PM
  • HDServices; did you figure out how to fix this?

    We have the *exact* same problem here.

    Moving to new database does not help.

    What do you get if you run:

    Get-MailboxDatabaseCopyStatus |  ft ContentIndexState

    ?

    • Proposed as answer by zhahn Thursday, August 22, 2019 6:07 PM
    • Unproposed as answer by zhahn Thursday, August 22, 2019 6:07 PM
    Thursday, August 22, 2019 9:19 AM
  • Found this and it fixed our issue --

    Hi guys, had the same issue over here but fixed it.

    I installed an Exchange 2019 (RTM) a few months ago and did the migrations without any problems. Now I have setup two Exchange 2019 CU1's, and I got this "Search is not up to date" error. I compared the RTM install with the CU1 installs and noticed the "Microsoft Exchange Search Host Controller" was stopped and disabled on the CU1's. I have set it to automatic, started the services, and now migrations complete without errors.


    Cheers Niels

    • Proposed as answer by zhahn Thursday, August 22, 2019 6:07 PM
    Thursday, August 22, 2019 5:57 PM
  • Hi H3ctiic,

    I get the result here: Get-MailboxDatabaseCopyStatus |  ft ContentIndexState

    "NotApplicable"

    -- Probably because we don't use DAG / Copy DB.

    2 weeks ago I started a MS support ticket, they are still investigating. Currently getting questions on and on, so I guess it will take another few weeks..

    Sunday, September 1, 2019 8:29 PM
  • Hi Zhahn,

    Thank you for sharing, This service is already on at our server, we don't have issues migrating from DB A to B, that goes OK. But our issue is that the search results are worse. But only sometimes. Alot of time it does work properly. But if it's not working OK for a word, it never works OK.


    In OWA the same search result is OK!

    Sunday, September 1, 2019 8:30 PM
  • Any update on this? Has MS been able to confirm this is a bug? Search not working in Outlook is of big concern for us as well and I am going to hold off until I know this issue is resolved.
    Wednesday, September 4, 2019 1:41 AM
  • Hi HDServices,

    We have the same issue. Did Microsoft team answer on your ticket

    Thursday, September 19, 2019 8:38 AM
  • We also have the same issue.
    We have both 2016 and 2019 Exch servers and doing migration by mailbox.

    So we have noticed

    • OWA and Outlook in cache mode works fine with partial search
    • Outlook in online mode does not perfom partial search
    • Advanced search in outlook works in both modes
    • Users, who have not been migrated to 2019 DBs does not have problem with search
    • Migration beetween 2019 DBs does not fix search
    • Migration from 2019 back to 2016 is fixing issue but we need to compleate upgrade procedure, so this not a solution

    The CU3 update was released in 17 Sep, maybe it will help ...

    Thursday, September 19, 2019 9:11 AM
  • Hi,

    we got the exact same issue. Outlook 2016 with Exchange 2019 CU2. In online mode, search does not work (does not find items if you enter partial search string etc.). Put Exchange in cached mode seems to solve the issue. The problem I have: we run an RDS farm so cached mode is not really an option because we would have tons of GB of OST files.

    Has anyone tried CU3?

    BR,
    Andreas

    Thursday, September 19, 2019 10:50 AM
  • A quick update: I have updated one of our DAG members to CU3 and let the clients connect to this server. Does not seem to help. So CU3 is NOT a solution :-(

    BR,
    Andreas

    Friday, September 20, 2019 4:00 AM
  • Hello all,

    I made a MS ticket on it; I primarly had the issue from Exchange 2010 (Exported boxes by Powershell to PST)

    And moved to a new domain with Exchange 2019 and imported by Powershell.
    First she asked me to import the .pst file through Outlook. That didn't help.

    Then she asked me to make an export FROM outlook on the problematic mailbox on Exchange 2019.
    And then do a re-import through Outlook. in the same box (Replace existing items)

    That fixed the issue for us. The search which did not work properly or showing incorrect results through Outlook, it is working now.

    So it seems when e-mail is getting from an old(er) Exchange version through Powershell Export, it is having the issue after importing in Exchange 2019.

    The Microsoft Support lady told me: She couldn't work on a fix, seems we are migrating from Exchange 2010 to Exchange 2019 (Not supported path). So the case is officialy closed as a bug and 'fixed' for us. Now we need to do manually open all boxes and export through Outlook and import through Outlook. (You can do this all on the new server)

    I will make time upcoming week to see if I can do a powershell export on Exchange 2019 and powershell import on Exchange 2019 if that also should do the trick. Will take less time than do box by box through Outlook. And also curious if the process is failing on the export part or import part.


    • Edited by HDServices Friday, September 20, 2019 10:38 PM
    Friday, September 20, 2019 10:37 PM
  • I just took a look over the thread and have asked some engineering team members if we know about this. If anyone has a case ID they can send me I'll look it up. grtaylor at the domain you would expect. 
    Saturday, September 21, 2019 9:01 PM
  • My ticket ID was 15838272
    Sunday, September 22, 2019 7:46 AM
  • Hi,

    we moved our mailboxes from 2016 to 2019 (moverequest) and got the issue. Export-Import is not an option for us (hundreds of mailboxes and about 1TB of store).

    Thx,
    Andreas

    Sunday, September 22, 2019 7:49 AM
  • I will be deploying EX2019 CU3 next week and migrating mailboxes from EX2013 CU23 - will test for this issue and open a ticket if I run into issues.

    Our users are mostly running in online mode, so switching them to cached mode is not an option.

    Exporting and Importing 3.5TB of mailbox data is not an option. I hope there is a fix for this on the horizon. 


    • Edited by techy86_ Sunday, September 22, 2019 5:55 PM
    Sunday, September 22, 2019 5:54 PM
  • I will test this week if it can be done through Powershell.
    Monday, September 23, 2019 7:29 AM
  • We have a bug open and are investigating this now. 
    Monday, September 23, 2019 3:16 PM
  • Hello!!

    Original poster here!!

    If anyone from Microsoft wants to see this bug 'in action' I am more than happy to help / show you via screen sharing session or whatever...

    Matt

    Monday, September 23, 2019 3:19 PM
  • We have a repro so we're all good. Thanks for the offer though Matt. 
    Monday, September 23, 2019 3:22 PM
  • We also have the same issue. We have done a migration from Exchange 2016 to Exchange 2019 in the same domain and now the searches are totally screwed. Hope that Microsoft will release a fix soon. 
    Tuesday, September 24, 2019 12:12 PM
  • Hi all,
    We opened a tick a few months ago on this issue and today they answered:

    The problem was officially acknowledged as a bug on our part and is handled accordingly in the product group.

    Unfortunately, I can’t give you a precise date when a solution will be published, but as soon as I hear something new, I'll forward you the information by e-mail.

    Тhe engineer in the mail said that a solution is possible in CU4 or CU5

    Thursday, September 26, 2019 12:48 PM
  • Thanks for the update
    Thursday, September 26, 2019 12:49 PM
  • CU4 or even CU5? What the heck? They want to leave us for 3 to 6 months with this problem?

    Has anyone a chance to accelerate this a little bit? Our users will not be amused...

    BR

    Thursday, September 26, 2019 1:15 PM
  • Altenratten do you have a ticket #? 

    Waiting until CU4 or CU5 is like saying it will be fixed in half a year, this isn't some low priority bug - search is easily the most frequently used feature in Outlook. This needs to be escalated to a hotfix of some sort.

    Thursday, September 26, 2019 8:46 PM
  • Hi,

    any news on this? Please don't let us wait for half a year for a fix. 

    Regards,
    Andreas

    Tuesday, October 1, 2019 6:41 AM
  • We have a bug open and it's being investigated. But I'm not going to indicate timelines, it's too early. 

    For future reference I'll throw a few things out there, and while I know I risk being flamed, I'm trying to help. 

    If you hit issues like this in the future you need to call support, not just put them in a forum or newsgroup. That's the best way to make sure we know about them as soon as possible, I only saw this thread as someone pointed me to it. Support cases being opened also increases priority of bugs - so if only one customers opens a case over an issue, unless someone really digs in, it looks like a one-off. Which will not get prioritized. So I encourage you to open support cases. 

    I'll also throw out there that Tech Community is another (and frankly, better) place to get attention. These forums are really not closely monitored as I think you know, Tech Community is going to get you more eyes.

    https://techcommunity.microsoft.com/t5/Exchange/ct-p/Exchange

    Just trying to help.

    Tuesday, October 1, 2019 3:51 PM
  • Thanks for this Greg, techcommunity link bookmarked.

    Are you able to confirm for us if running cached outlook is a workaround as pointed out by a few users? It would reassure some of us that are in the process of migrating many mailboxes.

    Tuesday, October 1, 2019 4:12 PM
  • I haven't tried to repro the issue myself, but from this thread it seems the issue only presents when Outlook is in Online mode. So I'd say if you are using Cached Mode (which we recommend) then you should be good. 

    If anyone who does repro this disagrees, please say. 

    Tuesday, October 1, 2019 11:44 PM
  • Yes in Cached mode it works fine... which is probably why it is a rare bug.. as most people would prefer to use Cached mode, I would go so far as to call it the default.

    The problem for us was... we use a database called Filemaker... and for some users... they use it over RDS.
    This works great for us BUT... when a user initiates a new email FROM Filemaker... the Outlook session is started and a new email opens... and you can press send... BUT in cached mode.. the email is NEVER actually sent! It just sits their in the users outbox indefinitely.  I do not know if this is a Filemaker bug or an Outlook bug.. I suspect the later.

    Anyway... after some trial and research I found that if i switch these remote desktop app users to have cached mode turned OFF... this fixes my problem... the new email is sent automatically all good no problems... (apart from the search bug)

    Wednesday, October 2, 2019 6:29 AM
  • I migrated from 2013 to 2019 and ran into some search issues, users with Outlook setup in "online mode" trying to do a partial search does not work at all for text email or PDF attachments. Switched to cached mode and it works.

    Looks like there are search bugs when running Outlook in non-cached mode.

    Greg, is a fix going to be released to make this work in online mode or must we run in cached mode?

    Tuesday, October 22, 2019 3:02 PM
  • We're still working on it. Cached mode is the workaround for now for those that can. 
    Thursday, October 24, 2019 9:57 PM
  • We just migrated to Exchange 2019 and are seeing similar search related issues. Our issue is as others noted that we don't use cached mode for about half of our users because they utilize RDSH sessions.

    Some notes that I also found:

    if I add a mailbox to my existing Outlook account as an additional mailbox to open, and I am using Cached mode, I still see incomplete search results, for the exact same items the user cannot find.

    If I do the same search in OWA -- the same results are still missing.  So it doesn't seem to be limited to only Outlook online mode either.

    I can open a support case with Microsoft, but it sounds like there is going to be no resolution still?

    Thursday, November 7, 2019 1:17 PM
  • Exchange Server 2019 CU3 is with problem on the search after apply CU3: "Time out for test thread".

    This troubleshooting is not working.: http://clintboessen.blogspot.com/2014/12/

    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\q2bwseec.fst\Microsoft.Exchange.BigFunnelFlow.28.dll' -- 'Error signing assembly -- Unknown error (8013141c)'


    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Ceres.ContentEngine.Admin.FlowService.IFlowServiceManagementAgent.PutFlow(String name, String serializedFlow)
       at Microsoft.Exchange.Search.Fast.FastManagementClient.AgentHandle`1.<>c__DisplayClass6_0.<PerformOperation>b__0(TManagementAgent agent)
       at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[TManagementAgent,TResult](AgentHandle`1 agentHandle, Func`2 function, String eventLogKey)
       --- End of inner exception stack trace ---


    Tuesday, November 12, 2019 7:17 PM
  • EvandroMalmsteen

    I am pretty sure this is a completely unrelated problem..........

    Wednesday, November 20, 2019 8:43 AM