Error in transaction log file of Exchange Server error

Transaction log files of any database are the repository of all operations being done; have details of each and every process activity. Even transaction log files of Exchange Server contain the details of committed, uncommitted, in progress, yet-to-complete data transactions. By looking at the log file, administrator can find out the root cause of the error problem and can take effective steps accordingly.

Moreover, transaction log files help in bringing the database to a consistent state. Therefore it is highly recommended to store transaction logs on a different drive to avoid disk failure consequences that can corrupt the database.

So when there is issue with log files related to writing of data to the drive, Exchange Server shows the indication of some kind of corruption in log files; which ultimately results in EDB file corruption.

Following error message appears in your Exchange Server, when there is error in transaction log file.

“Unable to create a new log file because the database cannot write to the log drive. Drive may be out of space or incorrectly configured. Check file system, drive space, and antivirus settings.”

This error is logged with event 413 in application event log.

Check for the error ids and decide on the possible solutions for the error. The possible reasons for the above error to occur depend on the error number described below:

• Error -1022 = Jet_errDiskIO: This error occurs due to general disk I/O errors that resist the access of requested database page or checking a file.
• Error -1032 = Jet_errFileAccessDenied: The error indicates that Exchange Server cannot access the file, probably because it is read-only or is in use by a process (virus checking or backup process).
• Error -1811 = Jet_errFileNotFound: The error -1811 implies that Exchange cannot found the log file because it is missing or has mismatching signature with the database. It can also occur if the log files are stored on unsupported network storage, failed drive or deleted by antivirus software.

Perform the following to resolve this issue; otherwise you need to perform Exchange database recovery:

• Make sure that the log drive file system is free from errors by running CHKDSK
• Check for system related problems in system log
• Check for the write permissions and available space on the disk
• Make sure that an antivirus software is not running
• Change the folders’ permissions containing information store file to default

You can hope that after performing above steps database gets consistent. If not, then use Exchange Recovery tool to get accurate and convenient Exchange database recovery. Software assures you complete Exchange .EDB database recovery irrespective of level of corruption in transaction log files.

However, if nothing works and you dont get your Exchange database back to healthy position, we suggest you use Exchange database recovery tool as this is the only option tthat assures you of accurate EDB database recovery. This Exchange database recovery tool is devised especially to repair and recover corrupt, inaccessible or damaged EDB database and recover the data accurately.

Additional articles about Exchange Recovery

About the author

Author of this article possess specialization in providing Exchange Server tips that include topics like Exchange database recovery, EDB repair, EDB recovery, Exchange recovery and many more. His articles enlighten the way to resolve various Exchange Server issues.

Please Rate This Article

Select Rating Excellent Very Good Interesting Fair Could Use Improvement

Number of ratings: 0
Rating: 0