Unhealthy Content Index Count
Issue: Content index errors may prevent you from performing DAG Database switchovers: “Error: An error occured while trying to validate the specified database copy for possible activation. Error: Database copy on server has content index catalog files in the following state: ‘Failed'”Resolution: The following Exchange Management Shell commands can be used to troubleshoot failed or corrupt DAG Database Content Index. These commands will identify and re-build/re-seed any bad content indexes associated with a healthy database.
Diagnose Exchange Search issues. 4 minutes to read. Contributors.In this articleApplies to: Exchange Server 2013Exchange Search indexes mailboxes and supported attachments in Exchange mailboxes. With increasing volumes of email, increasing mailbox sizes and storage quotas, provisioning archive mailboxes for users, and In-Place eDiscovery for performing discovery searches, Exchange Search is a critical component of the Mailbox servers in your Microsoft Exchange Server 2013 organization. Issues with Exchange Search can affect user productivity and impact In-Place eDiscovery functionality.To learn more about Exchange Search, see.Looking for management tasks related to managing Exchange Search? Using the Test-ExchangeSearch CmdletStep 5 of the procedure in this topic describes running the Test-ExchangeSearch cmdlet to help diagnose Exchange Search issues. You can use the Test-ExchangeSearch cmdlet to test Exchange Search functionality for a Mailbox server, a mailbox database, or a specific mailbox.
Keygen. The cmdlet delivers a test message to the specified mailbox (or to a database's system mailbox if a mailbox isn't specified), and then performs a search to determine whether the message is indexed, including the time taken to index it. Under normal conditions, Exchange Search indexes a message within about 10 seconds of the message being created or delivered to a mailbox. The test message is automatically deleted after the test.For detailed syntax and parameter information, see.
Unhealthy Content Index Count Is 1 (of 4 )
Retrieving unsearchable ItemsYou can use the cmdlet to retrieve a list of unsearchable mailbox items that couldn't be successfully indexed by Exchange Search. You can run the cmdlet against a Mailbox server, a mailbox database, or a specific mailbox. The cmdlet returns details about each item that couldn't be searched.
There are several reasons why a mailbox item can't be searched; for example, an email message might contain an attachment file type that can't be indexed for search or because a search filter isn't installed or is disabled. If a search filter for that file type is available, you can install it on your Exchange servers. ImportantSearch filters provided by Microsoft are tested and supported by Microsoft. We recommend that you test any third-party search filters in a test environment before installing them on Exchange servers in a production environment.For more information about unsearchable items, see:.Diagnose Exchange Search issuesYou need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the 'Exchange Search' entry in the topic.Check service state: Is the Microsoft Exchange Search (MSExchangeFastSearch) service started on the Mailbox server? If yes, go to Step 2. If no, use the Services MMC snap-in to verify that the MSExchangeFastSearch service is running as follows:.Click Start, point to Administrative Tools, and then click Services.In Services, verify that the Status for the Microsoft Exchange Search service is listed as Started.Check mailbox database configuration: Is the IndexEnabled parameter set to true for the user's mailbox database?
Unhealthy Content Index Count Sheet
If yes, go to Step 3. If no, run the following command in the Shell to verify that the IndexEnabled flag is set to true. Get-MailboxDatabase Format-Table Name,IndexEnabledFor detailed syntax and parameter information, see.Check mailbox database crawl state: Has the Exchange database been crawled? If yes, go to Step 4. If no, use Reliability and Performance Monitor to check the Crawler: Mailboxes Remaining counter of the MSExchange Search Indexes performance object.