locked
Exchange 2019 search isn't returning items RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have messages in a Exchange 2019 mailbox that will not be returned by search. The message in question has the number 12341 in the subject   (I can see it in my inbox) with two PDF attachments. When I search for 12341, the message is not returned using OWA or Outlook and online mode (meaning it's using the Exchange search index). If I run the same search query in Outlook cached mode (meaning it's using the Outlook search), the item is returned correctly.

    I ran get-FailedContentIndexDocuments against the mailbox and it returned several hundred items, none of which have a subject matching the message I mentioned. That said, when I've run the command after returning several hundred items it encounters an error "The component operation has failed." so I am not sure if the list of results I've gotten is complete.

    What can I do about this? Is there a way to rebuild the index in Exchange 2019?

    Thursday, January 24, 2019 7:39 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    You can use the same commands as exchange 2016 even though it is big funnel doing the indexing now in the mailbox itself. 

    Note indexing is now done at 3 places , when mail enters the mailbox, if it takes to long a event handler will pick it up again after a few seconds. if that takes to long the assistant will do a interval sweep. 

    if you look at your mailbox properties you should see there are some new properties containing bigfunnel. this displays the state of your search. 

    Get-MailboxStatistics email@address| fl *funn*,*MCDB*

    You can still test search with : Test-ExchangeSearch

    or 

    if you want to retry you can run:

    Start-mailboxassistant -identity <mailbox> -assistantname bigfunnelretryfeederimebasedassistant

    More info check the ignite session:

    https://myignite.techcommunity.microsoft.com/sessions/65646?source=sessions

    MCSA exchange 2016 | MCTS exchange 2013 | MCTS-MCITP exchange 2010 | MCTS-MCITP Exchange: 2007 | MCSA Messaging: 2003 | MCP windows 2000

    Thursday, January 24, 2019 7:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for getting back to me, Martijn. The cmdlet it you mentioned to start the mailbox assistant doesn't seem to exist on my Exchange 2019 server:

    [PS] C:\Windows\system32>start-mailboxassistant
    start-mailboxassistant : The term 'start-mailboxassistant' is not recognized as the name of a cmdlet, function, script file, or
    operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    At line:1 char:1
    + start-mailboxassistant
    + ~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (start-mailboxassistant:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

    I did a Bing search for that cmdlet name as well but unfortunately could not find it mentioned. Is there another one I can use?


    • Edited by Bobby Dore Friday, January 25, 2019 5:58 AM
    Friday, January 25, 2019 5:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bobby Dore,

    You can try to take steps below to recreate index for this database:

    1. Use command below to check which database hosted this mailbox:

    Get-Mailbox user | fl Database

    2. Stop MSExchangeFastSearch and HostControllerService services:

    Stop-Service MSExchangeFastSearch
Stop-Service HostControllerService

    3. Delete index folder for this database:

    4. Start MSExchangeFastSearch and HostControllerService services:

    Start-Service MSExchangeFastSearch
Start-Service HostControllerService
    5. Wait for some time(Depends on the size of your database), database will generate a new index file for this database.

    Regards,

    Kyle Xu

    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, January 25, 2019 9:22 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is Exchange 2019, it does not have such a folder. Index is inside the mailbox. 
    Friday, January 25, 2019 9:34 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Bobby Dore,

    Yes, in Exchange 2019 RTM, this index folder doesn't exist. However, this folder exist in Exchange 2019 preview: 

    In Exchange 2019 RTM, Microsoft re-engineered search using Bing. The search indexes are now within the database itself. As the index data is now within the database, normal log shipping includes the database and search data in a single replication and the index is always up to date on all database copies.

    It is more stable than before, in your scene, I would suggest you try to restart those two services, then wait for some time and try again:

    Regards,

    Kyle Xu

    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.

    Monday, January 28, 2019 2:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    if restarting the Services or the whole Server does not work, how do i recreate the search index?
    Friday, June 14, 2019 8:36 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Bobby. I have the same problem? How did you solve it? Thanks.
    Saturday, July 6, 2019 12:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am clearly suffering the same bug here :

    https://social.technet.microsoft.com/Forums/office/en-US/60aab333-0a33-4568-b2e7-a3ab0cedfc1d/search-bug-with-exchange-2019?forum=Exch2019

    Monday, July 8, 2019 6:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am clearly suffering the same bug here :

    https://social.technet.microsoft.com/Forums/office/en-US/60aab333-0a33-4568-b2e7-a3ab0cedfc1d/search-bug-with-exchange-2019?forum=Exch2019

    baseline seems to be: create a new database and move users over to recreate search index...
    Monday, July 22, 2019 3:48 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    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
  • Question
    Sign in to vote
    0
    Sign in to vote
    i noticed this with our Server too but starting the Service didnt do anything.
    • Edited by InfoCN Tuesday, November 26, 2019 10:12 AM
    Tuesday, November 26, 2019 10:11 AM