Manual Solution to Fix the Error
If you are facing, that in Exchange 2013 the copy of the database on this server was unexpectedly dismounted then this write-up if for you only. The Exchange Information store worker process crashes when the user tries to export mailboxes in MS Exchange server 2013. To fix this issue users need to install the Cumulative Update 2 (2859928) for their Exchange Server 2013. If this isn’t working for you and the problem still exists, the user has to disable the indexing for the database. From this user can see which part of the database is affected or the index is corrupted or not. Users can use the Exchange PowerShell command but before that first check the performance of the Exchange Server, all the settings/updates that were recently installed, and majorly the health of the server. Insert the following command to disable the index:Set-MailboxDatabase “Mailbox Database Name” -IndexEnabled $false
This command might degrade the performance or cause any other issue. To enable the index user has to replace the “false” part with “true”.
After this users have to stop the Exchange Search Service by using Exchange PowerShell.
Stop-Service MSExchangeFastSearch
Set-Service MSExchangeFastSearch -StartupType Disabled
Insert the command to set up the Exchange Search service to start automatically and then start the service:
Set-Service MSExchangeFastSearch -StartupType Automatic
Start-Service MSExchangeFastSearch
Wait for some time, even after that error still occurs then users have to re-index their database. For this run the new-mailboxrepairrequest cmdlet in the Exchange PowerShell against all active databases.
After that stop the MS Exchange Search and MS Exchange Search Host Controller Service. Then users have to rename the index folder which is given in the same folder where Exchange Database File kept.
Then start the Search and Host Controller service. It will occupy the new index. Now also if the users are facing the problems after trying everything. The only option left is that the user can move their existing database into another / new database.
If users think that the database is corrupted they can run the ESEUTIL tool to remove corruption from mailboxes. Then the user can move their database into the new one.
Users can use the Exchange Admin Center or the professional solution such as SysTools EDB Repair Tool to move the Exchange Database. If the user use EAC then while moving the database, again the Exchange Server will dismount the database and kill the process and you have to start the procedure from start.
This process is very time-consuming and the user might lose data. So, it is better to use the automated tool described in the above section.
Also Read: Fix the ‘Cannot Copy SQL Database File in Use’ Error Efficiently
Professional Solution to Fix “The Copy Of Database On This Server Was Unexpectedly Dismounted” Error
The EDB Repair Tool is capable to load dismounted / offline / damaged EDB files. This professional recovery manager for Exchange database software allows users to recover the highly corrupted Exchange Database file and repair Exchange Mailbox. Then the user can move their .edb file to the Live Exchange Server 2016 / 2013 / 2010 / 2007 / 2003 mailboxes.
User can also export multiple EDB file into PST / PDF / HTML / EML / MBOX / MSG / Office 365. Both the technical or non-technical users can use this software and perform their operation. The tool provides Quick and Advance scanning option that repair EDB file from corruption. According to the corrupted offline Exchange database file users can select the scan mode. Also, advance scan recovers permanently deleted EDB file & you can use this option to recover deleted mailbox after retention period.
The tool doesn’t consume time while moving the Exchange Database and it saves the user effort too. Also, the user doesn’t face any data loss.
Bringing It All Together
The solution provided in this write-up will help users to fix the error “the copy of database on this server was unexpectedly dismounted”. Users can use the manual solution mentioned in the above section to resolve the error but after some time the error shows up. Then it is recommended to use the professional solution, which will definitely solve a user problem.Also Read: Recover SQL Server Database Without Backups with This Guide
FAQs
Q. How do you fix the copy of database on this server was unexpectedly dismounted error?
A. SysTools EDB Repair Tool offers the professional solution for the error. The manual solution uses the New-MailboxRepairRequest cmdlet.
Q. Why does Exchange dismount the database unexpectedly?
A. Exchange dismounts databases without a clear reason, so admins struggle to find the root cause.
Q. What happens when all databases dismount?
A. Employees cannot access their mailboxes, which frustrates users and puts pressure on the IT administrator.
Q. Does the manual solution fix the error for good?
A. Not always. The error can show up again after some time, and then the post recommends the professional solution.