Database Has All Log Files Present
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool has determined that all log files that are required to recover this database exist and are in the correct location for recovery. Therefore, the recovery failure is not caused by a missing or mismatched transaction log file.
It is possible that the databases or transaction log files are damaged or that other files are interfering with the recovery process.
To correct this error
Use Exchange System Manager to mount one of the databases in the storage group and then view the Application log for errors that may indicate the cause of the failure.
Recover the database in isolation. After analysis of the database, the Exchange Server Analyzer will display the instructions for recovering the database in isolation.
Run Eseutil.exe /ML to verify the integrity of the required log files. For more information about how to use Eseutil, see Microsoft Knowledge Base article 248122, "How to use Eseutil to test transaction log files for damage in Exchange 2000 Server and in Exchange Server 2003" (https://go.microsoft.com/fwlink/?linkid=3052&kbid=248122).