Article ID: 249359
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q249359
SYMPTOMS
When one of the core .dat files is missing or corrupted, the message transfer agent (MTA) does not start. The internal Mtacheck that the MTA runs on startup does not write the appropriate error message to the Mtacheck.log file. Instead of letting the user know that one or more of the .dat files are missing or corrupted, the following error is written to the Mtacheck.log file:
A fatal MTA database server error was encountered. Call Microsoft Product Support.
RESOLUTION
Copy any missing .dat files from the Bootenv folder on the CD to the Mtadata Database folder. Compare the .dat files in the Mtadata folder to the following:
Db000001.dat through Db000009.dat
Db00000a.dat through Db00000f.dat
Db000010.dat through Db000019.dat
Db00001a.dat through Db00001f.dat
Db000020.dat through Db000026.dat
Also, if the Db000001.dat file is 0 bytes, that file is most likely corrupted and you will need to restore it from backup. If there is no backup of the Db000001.dat file, it is likely that mail that has been secured to a queue will be lost. This is because this file is responsible for keeping track of which messages are secured to a particular queue.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
MORE INFORMATION
You will also see an error with Event ID 2152 in the application log when the MTA will not start because of a problem with the .dat files
Additional query words: exch2kp2w
Keywords: kbbug kberrmsg kbnofix KB249359
