Exchange Server error 2140 resolved

Read time 3 minutes

At times, when attempting to start the Microsoft Exchange Message Transfer Agent (MTA) service, you may encounter the following error message on your computer screen:

To address the error message mentioned earlier, when you run the MTA database integrity checker utility (Mtacheck.exe), instead of resolving the error, the utility presents the following error message:

Database contains serious errors and cannot be automatically repaired

In addition to the previously mentioned error message, the application event log also records the following events:

Description MSExchangeMTA – A critical database error has occurred, resulting in an unsuccessful database recovery operation. Manual correction is necessary. For more information, refer to the file: drive:\Exchsrvr\Mtadata.\MTACHECK.OUT\MTACHECK.LOG. We recommend reaching out to Microsoft Product Support Services for further assistance. [DB Server MAIN BASE 1 14] (16)

Description: An MTA database server error was encountered. Error accessing object attribute (AAT) on a Read/Write operation. Filename: drive:\Exchsrvr\Mtadata\.\DB000068.DAT. File operation: 0. Operating system error: 2127. Referenced object: OPEN (00000000 => N/A). Referenced object error 00000000. [0 DB Server OPERATOR 22] (14)

Description: An MTA database server error was encountered. Failed to read attribute information (AAT) for object 01000068. Database server error code: 2127. [DB Server OPERATOR 22 29] (14)

Description: An MTA database server error was encountered while attempting to unlock an object which is not locked. Called from MTA. Procedure 460. Object at fault: 06000174. [DB Server DISP: ROUTER 16 58] (14)

Description: The MTA is running recovery on the internal message database because the MTA was not shut down cleanly. This operation may take some time. Status updates will be written to the Windows NT Event Log. [%1 %2 %3 %4] (14)

The error message mentioned earlier stems from an incorrect path value for the MTA database stored in the Windows registry.

Solution

To resolve the error message mentioned above, you need to edit the registry to specify the correct path for the MTA database. The following steps will guide you through the process of specifying the accurate location of the MTA database in the Windows registry:

1. Click Start > Run. The Open dialog box appears.
2. Type regedit in the Open box and click OK.
3. Locate the following registry entry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Database Path
4. Double-click the located registry entry and specify the correct MTA database location in the Value data box.
5. Now, locate the following registry entry:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Run Directory
6. Double-click the located entry and verify the location of MTA Run Directory in the Value data box.
7. Click Exit to close the registry editor.
8. Restart the Exchange Server.

If the issue persists despite following the previous steps, you can seek assistance from Kernel for Exchange Server recovery software. This efficient software conducts a thorough scan of the Exchange database file and automatically rectifies any underlying problems. It excels in EDB file recovery and is compatible with MS Exchange Server 2019, 2016, 2013, 2010, and previous versions. With EDB to PST conversion capabilities, it allows you to restore Exchange mailboxes and save them as PST files.