Fixing "Error 2140. Internal Windows NT error..." Error

Fixing "Error 2140

Fixing "Error 2140. Internal Windows NT error..." Error

There are numerous reasons responsible for corruption in Microsoft Exchange Server database, one of them being scanning through an anti-virus software. If an anti-virus software detects any virus in the Exchange database, then it removes and/or places the log file in the recycle bin or quarantine folder. This totally depends upon the configuration of that anti-virus software. However, after doing so, the sequence of the log files changes, which further causes inaccessibility of data saved in the database. In such cases, if the user wants to access the database, then s/he needs to opt for an updated backup of the database or use Eseutil command. However, if no backup is available and the repair command fails to repair the database, then the user needs to opt for an a commercial Exchange Server Recovery software.

To illustrate the above problem, consider a practical scenario. You installed a new anti-virus software to scan your database and remove all viruses (if any). However, after the anti-virus software completes its scanning, you encounter the below error message:

"Error 2140. Internal Windows NT error.

The following Event ID is then generated in the Windows NT Event Viewer Application log:

Event ID: 7024

Source: MSExchangeIS

Type:Error

Description:

The Microsoft Exchange Information Store stopped with Service Specific Error 4294966781."

The error message makes the data saved in the Microsoft Exchange Server database inaccessible.

Cause:

The root cause for the above error message is corruption of database after anti-virus scanning. To prevent database from being corrupted after anti-virus scan, you should make sure that all the Exchsrvr directories are excluded from scanning.

Resolution:

To get past the above error message and to access the database, you will need to restore the log file and access the data saved in the Information Store. However, if the above measure fails then you will need to repair the database using a third-party Exchange Server Recovery application.

An Exchange Database Recovery application uses effective repairing methods to repair logically corrupted databases and restore them at required location. The original database does not get altered during the repair process.

Stellar Phoenix Mailbox Exchange Recovery is a powerful, yet safe recovery tool that systematically recovers all logically damaged databases. The recovered mailboxes from the database are stored in .pst file format. Designed for Windows 7, Vista, XP, 2003, and 2000, the Exchange Recoverytool supports Exchange Server 5.5, 2000, 2003, and 2007.

POST COMMENT

Credit Repair Solutions Flood Damage Repair In Breckenridge Silverthorne or Summit County How To Use A Credit Repair Company Using A Credit Repair Service Bluetooth Headphones: A Quick Guide to Setting Up Your Headphones in Windows XP Three types, three eras – where did your sash windows come from? Manage Debt for Credit Repair Success Pvc Pipes and Fittings Products - PVC Pipe For Home Repair Unique Dent Repair Services For Your Vehicle Let Replacement Windows reduce your Power Bills! Car Window Cleaning 101 - How To Effectively Clean Your Car Windows Remove Vista Guardian 2010 - How to Remove Vista Guardian 2010 Completely Remove Antivirus Vista 2010 - How to Remove Antivirus Vista 2010 Completely