| Event Id | 2171 |
| Source | MSExchangeMTA |
| Description | An MTA database server error was encountered while reading an attribute. Called from <directory name>. Procedure: <name>. Database error code: <error code>. Object at fault: <object name>. Attribute identifier: <id>. Value number: <value>. Referenced object |
| Event Information | According to Microsoft: CAUSE 1.: The Dbserver.sch file in the MTADATA directory is pre-Service Pack 1 (46,787 bytes). The size of the correct version is 46,777 bytes. RESOLUTION: 1. Check the size of the Dbserver.sch file by going to Windows Explorer, clicking the File menu, clicking Properties, and clicking Size. If the file size is 46,787 continue with the following steps. 2. Stop the message transfer agent (MTA) and Internet Mail Service. 3. Copy the Dbserver.sch file from the Exchange Server SP1 CD to \exchsrvr\mtadata. 4. Run mtacheck /rp. If you do not run MTACHECK, then messages may still back up. 5. Run mtacheck /rd. 6. Restart the MTA service and Internet Mail Service. 7. Send test messages. 8. Watch the MTA queue between the servers to confirm that messages are not backing up. 9. Also, you must apply latest service pack for Exchange 5.0.According to Microsoft: CAUSE 2.: 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. CAUSE 2: This issue can occur if one or more .dat files from the \Exchsrvr\MTAData (MTA Database) directory are missing when you attempt to start the MTA. RESOLUTION : To r |
| Reference Links | XCON: No Message Flow Between Servers: IDs 1097, 2124,2171 XCON: Corrupted Message in MTA Database Logs Database Server Errors in App. Log Error Message Occurs When Starting the Message Transfer Agent Q163326 :How and Why to Run Mtacheck |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.