How can I resolve event 412 on an Exchange server?

Most Exchange database issues (including corruption) occur because the administrator continues to use the very old hardware without renewal. It is therefore suggested to check the application log and related information in a timely manner. Once the corruption of the EDB database is confirmed, the administrator can restore from a good backup or select an EDB restore option.

To understand such situations, we need to consider an issue when you are unable to mount the Exchange database. You notice that all Exchange services are working error-free, but when you try to mount the database it reports an error like below:

Event type: error

Event Source: ESE

Event category: logging / recovery

Event ID: 412

Date: 3/7/2008

Time: 13:40:37

User: N / A

Computer: SMTPBRMDBALEX2

Description:

Information Store (4948) e53f288d-df1b-47ba-9c3b-901e530848a5: Unable to read the header of log file E: exchangesrvr mdbdata E003C9F3.log. Error -530. The error indicates that it cannot read the log file header.

Cause

Error -530 specifically occurs due to mismatched log files signature. The log file signature allows Exchange to play a correct set of log files. Each database header contains this signature information from the current log file. If these values ​​do not match, error -530 occurs which indicates the same.

Solution

To fix the existing -530 error problem, you need to implement solutions like:

1. Restore from the last backup of the Information Store. Rename the damaged EDB and STM database and create new databases to recover lost data from a backup.

2. Open the command prompt and navigate to the Exchange Server directory (usually C: Program Files Exchsrvr BIN). Then run Eseutil / P for the damaged database.

The command removes damaged pages and creates unused space. So you need to run the Eseutil / D command to defragment the database and then run isinteg -fix repeatedly until you don’t get any errors or get the same errors after twice.

After performing the hard repair via the Eseutil / P command, the database may not be stable because data loss is likely. Therefore, it is recommended to move the mailboxes to a new database or run third party EDB repair software instead of performing the hard repair. The EDB repair tools are exclusively built products designed to scan and repair the damaged Exchange databases.

The EDB repair Tool is a professional utility that repairs the damaged EDB database and provides a selective mailbox recovery option as * .pst files. The EDB repair software has an interactive design that makes it easy to operate. The tool supports Exchange Server 5.5, 2000, 2003 and 2007.



Source by Axel Culver