| Event Id | 2188 |
| Source | MSExchangeMTA |
| Description | An MTA database server error was encountered while deleting an object. Called from <directory name>. Procedure <name>. Database error code: <error code>. Object at fault: <object name>. [<value> <value> <value> <value>]1 <name> <error code> <object name> |
| Event Information | According to Microsoft: CAUSE : When you analyze the application log and look at the details of all these Event IDs, it becomes obvious that "object at fault" in each Event ID is pointing to the same message object, a corrupted message. In the Event IDs above, this is the Db000034.dat file, which is located in the MTA database folder. RESOLUTION : Even though the above Event IDs state the "Object does not exist," it may exist in the Mtadata folder. If the corrupted file (Db000034.dat in this example) still exists in the Mtadata folder: 1. Stop the MTA service. 2. Rename or remove this file from the Mtadata folder. 3. Run the Mtacheck utility twice. 4. Restart the MTA. If the message file does not exist in the Mtadata folder: 1. Stop the MTA. 2. Run Mtacheck twice. 3. If Mtacheck registers that the MTA is clean, restart the MTA. |
| Reference Links | Corrupted Message in MTA Database Logs Database Server Errors in App. Log Troubleshooting Tips for: Exchange MTA Not Starting How to Troubleshoot MTA Starting Failures |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.