.edb repair

Transaction log file acts as a storage location for the entire uncommitted Exchange database information. If your EDB files gets crashed, transaction log files works as a boon since it helps you bring the database back to a liable state. Since it is so beneficial, it is always suggested to keep transaction logs at a different location, for avoiding disk failure which could hinder the proper functioning of exchange server database. However, sometimes Exchange server encounters problems while writing data to the log files and throws several errors like Unable to create a new log file error.

Let us consider a practical scenario in which you encounters the following error with the Exchange server:

"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."

Why 'Unable to create a new log file' error occurs:

The causes responsible for this Exchange server error mainly depends upon the error number displayed in event description. If you are getting Error -1022 =Jet_errDiskIO , it indicates that the error has occurred due to disk I/O errors which stops you from accessing the requested page. Error -1032= Jet_errFileAccessDenied shows that your Exchange server could not access the requested file, since it is being used by another process or is read-only. Occurrence of Error -1811 = Jet_errFileNotFound, indicates that Exchange server could not find the log file since it is missing or having a mismatching signature. Such problems can also occur due to failed drive, like disk concerns, system issues, application malfunctioning, antivirus problems, unsupported network storage etc.

How to fix 'Unable to create a new log file' error:

• As corruption leads to the occurrence of various types of problems, first of all check out if log drive is free from errors with the help of chkdsk command
• Also check for the system-related issues present in system log
• You have to verify for write permissions and also check out for the free space present on your system
• Check out if antivirus programs are not running
• Also try by changing folders permissions which are containing information store file

You can also try to fix the error by using eseutil /p and isinteg -fix commands, but it fails in most of the cases and also results in deletion of files. However, if all these methods fails to repair Exchanger server database safely and fix Unable to create a new log file error, you have to go for third-party EDB repair applications. These third-party applications are especially designed to overcome all types of Exchange server problems in a few clicks. The software helps you perform Corrupted EDB repair very efficiently so that you can perform necessary tasks using Exchange Server.