Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A fatal database error occurred, the database recovery operation was not successful and manual correction will be required. Details can be found in the file: C:\exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. Please contact Microsoft Technical Support. [DB Server MAIN BASE 1 14] (16)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
This issue may occur if incorrect values exist for the location of the MTA database path in the registry. See ME324026 for more details.
As per Microsoft: "The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full". See MSEX2K3DB for more details.
Even though the article ME249359 applies to Exchange 2000, it fixed my problem for Exchange 5.5.
As per Microsoft: "The MTA is attempting to perform an online MTACHECK during startup, and an existing Mtacheck.log file located in the \Exchsrvr\Mtadata\Mtacheck.out directory may be corrupt. Additionally, the MTA may fail to start if the Mtacheck.log file is marked as read-only. This flag should never be set by the MTA itself. ". As per ME169918 this problem has not been fixed yet.
In my case, it turns out that \mtadata\Db000001.dat was corrupt. Copy that file from the CD, make sure Read Only is turned off, and run mtacheck.exe.
|Private comment: Subscribers only. See example of private comment|
|Links: ME169918, ME249359, ME324026, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated