Sign in
 

none
Content Index State RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Running Exchange Server 2016 on Windows Server 2012 R2.

    The Content Index State continually changing to Failed, if get further information the issue reported is;

    The Microsoft Exchange Search Host Controller Service is not running on server

    Check the service and he Microsoft Exchange Search Host Controller Service is running on server, so do not know how to fix. Have tried stopping both Search services and deleting the GUID folder, then restarting the services but this does not seem to help.

    Friday, July 19, 2019 2:30 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    What CU are you on? And are you running any backup jobs? I've seen some backup processes (like Symantec) cause the index to go to a failed state, and come back to healthy after the job is complete.

    My Blog: http://exchangeitup.net My Twitter: http://twitter.com/ExchangeITup

    Friday, July 19, 2019 3:03 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    What's the detailed version of your Exchange 2016? This command will help you get the detailed version:

    Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion

    Is the content index state of all databases failed?

    Please make sure the Startup type of Microsoft Exchange Search and Microsoft Exchange Search Host Controller services are set to Automatic.

    Use Event Viewer to check the Application event log for some related error messages.

    Please also take StaceyBranham's suggestions into consideration, check if the backup is performed.

    Regards,

    Lydia Zhou

    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:10 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Exchange 2016 CU11, we hope to update to CU13 soon especially if it fixes this issue.

    We have not had this issue since migrating to Exchange 2016, but recently (maybe since we updated to CU9 or CU11) we have been seeing this issue on a number of servers.

    Monday, July 22, 2019 10:17 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    That's OK if you want to upgrade to Exchange 2016 CU13. Hope something may be fixed during the upgrade. After you restart the server, please first to check and make sure all Exchange services work well.

    Here are some points you must pay attention to before upgrading to Exchange 2016 CU11:

    1. Requires Microsoft .NET Framework 4.7.2
    2. Download and install Visual C++ Redistributable Packages for Visual Studio 2013.
    3. Need to run the cumulative update setup program with the /PrepareAD parameter.

    You can check these for more information and requirements about Exchange 2016 cu13: Cumulative Update 13 for Exchange Server 2016, Exchange 2016 CU13 Released

    Regards,

    Lydia Zhou

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

    Wednesday, July 24, 2019 9:44 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Just checking in to see if above information was helpful. Please let us know if you would like further assistance. 

    Regards,

    Lydia Zhou

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

    Tuesday, July 30, 2019 2:18 AM
    |
    Moderator