[Fixed]: Dismounted Database Error MSExchangeFastSearch Code 1009

Ram Infotech Data Recovery March 21, 2024

          [Fixed]: Dismounted Database Error MSExchangeFastSearch Code 1009

Summary: Sometimes, you encounter the MSExchangeFastSearch error (Event ID 1009) with the message stating that indexing of the database encountered an unexpected exception. In this post, we will see how to resolve the MSExchangeFastSearch error in Exchange Server. We will also mention an Exchange repair tool that come in handy in case the database gets corrupted or not mounting.  

In Exchange Server with a Database Availability Group (DAG) 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.

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.

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.

Below, we will see how to troubleshoot the MSExchangeFastSearch (code 1009) error in Exchange Server.

How to Resolve Dismounted Database Error MSExchangeFastSearch Code 1009?

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 error.

Solution 1 – Check the Indexing State

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 as given below.

Solution 2 – Creating a New Active Directory Group

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

  • Open the Active Directory Users & Computers.
  • Create a new Security Group, called ContentSubmitters.
  • Add the following members to the group and give them full rights to the group:
    • Administrators
    • Network Service
  • After the replication of the Active Directory on all Active Directory servers, restart the following services:
    • Microsoft Exchange Search
    • Microsoft Exchange Search Host Controller
  • After this is complete, check the event logs to see if the problem is resolved.

To Conclude

Above, we have discussed the MSExchangeFastSearch error (Event ID 1009) and mentioned some possible solutions to resolve it. However, if you have Exchange Server Cumulative Update 4 or 5 installed, you can ignore the error message or install the Cumulative Update 6 for Exchange Server 2016. This update can repress such messages. However, you need to be careful when installing the update. If something fails during or after the installation, the database would not mount or the Exchange Server services become unusable. In such cases, you need the best tool to recover the data. Stellar Repair for Exchange is one of the best tools to recover data from corrupted Exchange database or the database which is in Dirty Shutdown state. It can granularly export the EDB data to PST and other file formats. It can also export the data directly to another database in your Exchange Server, migrate to a new Exchange Server, or export to Office 365.

 

 

 

 

Ram Infotech Data Recovery

Posted by Ram Infotech Data Recovery

Post a Comment

0 Comments