Shulou(Shulou.com)06/01 Report--

This article shows you how to solve the problem that the exchange2013 database can not be loaded. The content is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

A user, whose mail system is exchange2013, does not back up the database regularly, resulting in the continuous growth of log capacity, and the partition capacity of one of the databases is exploded. at that time, the user manually transferred some of the logs to a temporary directory. More than 200 GB of partition space has been freed, and the database still cannot be loaded.

The event log reported an error as:

MapiExceptionDatabaseError: Unable to mount database. (hr=0x80004005, ec=1108) Diagnostic context: Lid: 65256 Lid: 10722 StoreEc: 0x454 Lid: 1494-Remote Context Beg-Lid: 45120 dwParam: 0x915D7628 Lid: 57728 dwParam: 0x915D7667 Lid: 46144 dwParam: 0x915D7ADB Lid: 34880 dwParam: 0x915D7ADB Lid: 34760 StoreEc: 0xFFFFFDE3 Lid: 41344 Guid: 2a2855dc-18b6-4538-9182-f595330a6876 Lid: 35200 dwParam: 0xA6F0 Lid: 46144 dwParam: 0x915D7D5C Lid: 34880 dwParam: 0x915D7D5C Lid: 54472 StoreEc: 0x1388 Lid: 42184 StoreEc: 0x454 Lid: 1750-Remote Context End-Lid: 1047 StoreEc: 0x454 [database: XXDB Server: MailDB01.xxxx.com]

The above is the status after contacting the user.

During the troubleshooting process, first of all, make sure that there is enough available space in the current partition. Second, check that the database shutdown status is dirtyshutdown. Use eseutil for repair, which takes 50 minutes, prompting you to complete the repair successfully. Manually mount the database, still prompting that the database cannot be loaded. Repair again, using mout-database-force to force mount the database, which still fails. To find KB, you need to move all logs (.log) and checkpoint files (.chk) of the path where the database is located to a temporary directory. Because the user has not backed up the database for a long time, there are as many log files as 1TB, and the log files take 8 hours to migrate. After the migration of log and checkpoint files is completed, the database is loaded automatically and the problem is solved.

One thing to note is that all * .log files need to be removed. Remind everyone that the database must be backed up regularly.

The above content is how to solve the problem that the exchange2013 database cannot be loaded. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.