{"id":162049,"date":"2024-02-14T06:10:43","date_gmt":"2024-02-14T06:10:43","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=162049"},"modified":"2024-02-14T08:18:42","modified_gmt":"2024-02-14T08:18:42","slug":"fixed-dismounted-database-error-msexchangefastsearch-code-1009","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/fixed-dismounted-database-error-msexchangefastsearch-code-1009\/","title":{"rendered":"[Fixed]: Dismounted Database Error MSExchangeFastSearch Code 1009"},"content":{"rendered":"

In Exchange Server with a Database Availability Group (DAG)<\/a> setup, on the lagged database copies, you may encounter an error message stating that indexing of the database encountered an unexpected exception. A lagged copy is a passive copy of the active database where the replay time of the transaction logs is more than the default time.<\/p>

When you check the Event Viewer on the server which is hosting the lagged copy of the active database, you may notice a message similar to the below.<\/p>

Log Name: <Log Name>
Source: MSExchangeFastSearch
Date: <Date>
Event ID: 1009
Task Category: General
Level: Warning
Keywords: <Keywords>
User: N\/A
Computer: <Computer Name>
Description:
The indexing of mailbox database <Database Name> encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: \"Feeding was skipped for <Database ID> due to the state 'Unknown', error code: 'Unknown'.\"<\/code><\/p>

When you go through the Exchange Server functionality, you will find that there are no visible issues and everything is working fine. However, the event logs will still be flooded with the event. When you test the search and indexing, you will still find no visible issues.<\/p>

Below, we will see how to troubleshoot the MSExchangeFastSearch (code 1009)<\/strong> error in Exchange Server.<\/p>

How to Resolve Dismounted Database Error MSExchangeFastSearch Code 1009?<\/h2>

Before starting the troubleshooting, check what has changed on the server from the audit log. This will help to understand if there was something which had impacted the server. Apart from this, you can restart the Microsoft Exchange Search services to see if this resolves the problem. If the problem is not resolved, follow the below solutions to fix the MSExchangeFastSearch<\/strong> error.<\/p>

Solution 1 – Check the Indexing State<\/h3>

From the error message, it seems the problem is related to search. You need to check the indexing state and see if there is any issue with indexing of items and mails. But before this, check if the event log is also present on the server where the active database is and if there are any events logged in other servers hosting the passive (not lagged) copy of the active database. If there is no mention, test the replication of the database to ensure that there is nothing wrong. For this, use the Test-ReplicationHealth command<\/a> as given below.<\/p>

Test-ReplicationHealth -Identity <server name><\/code><\/p>

\"Test<\/figure>

If all is fine, confirm that the indexing is working well. For this, you can run the following Get-MailboxDatabaseCopyStatus command<\/a> in the Exchange Management Shell (EMS).<\/p>

Get-MailboxDatabaseCopyStatus * | Sort Name | Select Name, Status, ContentIndexState<\/code><\/p>

\"Get<\/figure>

The ContentIndexState <\/strong>can be Crawling, Healthy, or FailedAndSuspended<\/strong>. Depending on the health status, you can try the troubleshooting solutions.<\/p>

Solution 2 – Creating a New Active Directory Group<\/h3>

You can also try to create a new Active Directory group and restart the Microsoft Exchange Server services related to search. Follow these steps:<\/p>