SYMPTOMS:

If you try to start the Microsoft Exchange Message Transfer Agent (MTA) service, you may receive the following error message:

Could not start the Microsoft Exchange Message Transfer Agent service on \\ServerName. Error 2140: An internal Windows NT error occurred.
If you try to run the MTA Database Integrity Checker Utility (Mtacheck.exe), you may receive the following error message:

Database contains serious errors and cannot be automatically repaired.
Additionally, you may see the following events in the Application event log of Windows NT Event Viewer:

Event ID: 2152:
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System
Description:

MSExchangeMTA - 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: drive :\Exchsrvr\Mtadata\.\MTACHECK.OUT\MTACHECK.LOG. Please contact Microsoft Product Support Services. [DB Server MAIN BASE 1 14] (16)

Make copies of your mdbdata folder before you do anything Microsoft says!

How to start With A New Database

Stop and call us Now! We can help immediately!

Call our Exchange Hotline 727-251-2058 24/7 - Initial Support Call Are No Charge. You Only Pay If An Engineer Must Remote In To Solve Your Exchange Issue.

Exchange Recovery Experts.

Exchange Error 2140 Support Forum

Event ID:2127
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Operating System
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)

Event ID:2155
Event Type: Warning
Event Source: MSExchangeMTA
Event Category: Internal Processing
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)

Event: 2187
Source: MTA
Type: Warning
Cat: Internal Processing

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)

Event ID: 2219
Source: MSExchangeMTA
Category: Field Engineering
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)
CAUSE
This issue may occur if incorrect values exist for the location of the MTA database path in the registry.

RESOLUTION

To resolve this behavior, edit the registry to refer to the correct location for the MTA database files. To do so, follow these steps:

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
Locate the following registry entry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Database Path

Double-click the registry entry that you located in step 3, and then type the correct path to the MTA database files in the Value data box. For example, drive:\exchsrvr\mtadata.
Locate the following registry entry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeMTA\Parameters\MTA Run Directory

Double-click the entry that you located in step 5, and then verify that the correct location for the MTA Run Directory is displayed in the Value data box. For example, drive:\exchsrvr\mtadata.
On the Registry menu, click Exit to quit Registry Editor.
NOTE:You can also use Microsoft Exchange Server Performance Optimizer to move the MTA database files. To start Performance Optimizer, click Start, point to Programs, point to Microsoft Exchange, and then click Microsoft Exchange Optimizer.

Stop and call us Now! We can help immediately!

Toll Free 1-866-438-6932

Direct: 1-727-345-9665.

Exchange Recovery Experts.

To start with a clean database do the following. Make sure to copy the mdbdata folder so we can recover your mailboxes and you can exmerge them into your new database.

If you already have run an eseutil /p on your directory you really have two options;
1. Restore the directory from tape or
2. Start with a blank directory

Running an eseutil /p repairs the database the same way scandisk repairs a drive. If it finds information that is doesn't understand it removes it. It is never recommended that you leave a slash p'ed database in production as the eseutil could have removed structure from the database that will make if fail over time.

Restore just the directory service first. If it starts great move on to the Information Store. You may have to repair or restore the Information Store also. If the directory service does not start after a restore then you will have to reinstall Exchange to get a new one. You can still attempt to start your old information store though;
1. Copy or rename the MDBDATA directory on all drives, thereby backing up the Information Store
2. Verify that you know the org,site, service pack, and service account, so we can rebuild the server and attempt to restore the DS.
3. remove Exchange 5.5 completely
4. Reinstall same org, site, service pack, and service account/password. Once installed create a blank Internet Mail Service (IMS) if there was one before.
5. Restore your Directory service if you can. Stop the DS first and copy the DSADATA directory, so that you have a backup of the fresh install directory and then you will not have to uninstall and reinstall again to get a fresh dir.edb.
6. Otherwise, stop the Information store and clear out the fresh install MDBDATA directories.
7. Copy or rename the old MDBDATA directories
8. Attempt to start the IS (Should get a -1011)
9. goto the command line run isinteg -patch from the exchsrvr\bin directory
10. Start the store
11. Open the Exchange Administrator and expand to the private store look in the mailboxes. There you will see that mailboxes on the store but if you look in recipients they will not be present(This is of course if we are running a fresh install directory, otherwise they will be there and you are done).
12. Goto the properties of the server and select the advanced tab
13. Click Consistency Adjuster
14. Select Sync option on both the Public and Private
15. Select the radio button for ALL Inconsistenties
16. click apply this will create directory objects for all the mailboxes on the store.
17. You will have to relink each created mailbox to the correct NT account
18. You will have to reenter any directory information such as phone numbers and physical address
19. You may also need to install an IMS again if there was one before.