Read time 3 minutes
JET engine errors in Microsoft Exchange Servers are the most complicated errors that are often not repairable with the Eseutil or other manual approaches. If you have also encountered Exchange Server error 2140 or 0xFFFFFE02 JET_errLogWriteFail, you know how tricky it is to resolve the issue and restore Exchange Server.
At times, when attempting to initiate the directory service on a Microsoft Exchange Server, you may encounter the following error message prominently displayed on your computer screen:
Unable to initiate the Microsoft Exchange Directory service on \SERVERNAME, encountering Error 2140: An internal Windows NT error has occurred.
When the preceding error message occurs, the following events are logged in the Application log:
Event ID: 109
Source: ESE97
Type: Information
MSExchangeDS (988) the database engine is replaying log file R:\LogFiles\DSAData\edb.log.
Event ID: 110
Source: ESE97
Type: Information
MSExchangeDS (988) the database engine has successfully completed recovery steps.
Event ID: 0
Source: ESE97
Type: Information
MSExchangeDS (988) -510
Event ID: 1166
Source: ESE97
Type: Information
Error -510 has occurred (internal ID 2030148). Contact Microsoft Technical Support for assistance.
Event ID: 1002
Source: ESE97
Type: Information
The Microsoft Exchange Server database (EDB) could not be initialized and returned error -510. Unrecoverable error, the directory can’t continue.
Reason for 0xFFFFFE02 JET_errLogWriteFail
The error number -510 in the preceding events refers the JET_errLogWriteFail message. This error message generally occurs when:
- The .log file gets damaged due to a virus or during an export offline EDB to Office 365 mailbox process.
- If a controller or hard disk does not respond to the disk commands, the server may encounter JET error 510.
- Inappropriately configured antivirus can lock the AD log files leading to JET engine error.
- An internal server hardware issue or a software bug can also cause the issue.
How to identify 0xFFFFFE02 JET error on your server?
Here is what points out to error on the server:
- You are unable to mount the dismounted database again.
- Email or database services (corrupted Information Store Services) aren’t starting.
- Database engine is showing errors when writing new data in log files.
- Storage drive does not have any more space to hold transactional logs.
How to Troubleshoot 0xFFFFFE02 JET_errLogWriteFail Error?
Following steps will help you to resolve the specified error message from the Exchange database:
- Backup the current database either in offline mode or in online mode.
- Now, you need to check the consistency of Dir.edb file. You can check the consistency of Dir.edb file by executing the following command:
- After executing the command, check the output to notice the state of Dir.edb file. If the output states, the file is consistent, remove all .log files and start the directory service. But, if the Dir.edb file is found inconsistent, then restore it from the backup.
- If you restore the Dir.edb file from online backup, then replay the transaction logs that are older than the current damaged transaction log. But, if you restore the Dir.edb from offline backup, then remove the database and transaction log directories and restore the Dir.edb file only.
eseutil /mh Dir.edb
Other Solutions to Fix the Error 0xFFFFFE02 JET_errLogWriteFail
Common troubleshoots you can try to remove 0xFFFFFE02 JET_errLogWriteFail error:
- Restart the Server: It’s one of the most basic solutions you may try. Sometimes, a minor internal hardware issue, like a resource deadlock, may be preventing the database from accessing the log file. A simple reboot will release the deadlock and fix the problem. Also, check and update any outdated software to remove any software glitches.
- Modify Antivirus or Firewall Setting: The anti-malware program installed on your system has complete access control over the data. If due to any reason the antivirus or firewall of your system interprets the database log files as dangerous, the antivirus will immediately quarantine them. Therefore, disable the antivirus program or mark the log files as safe to cure the problem.
- Check Storage Space: The error can also arise due to hardware issues. If your hard disk, containing the EDB file and log files, is 100% full, then it can behave abnormally. Therefore, it’s always recommended to have at least 10% free space available at all times to avoid any problems. If your hard disk is full, free some space from it or increase the storage space. Alternatively, you can migrate EDB to Live Exchange, which offers real-time scalability and prevents such errors from occurring.
- Repair Exchange Database:Another method that an Exchange database administrator can opt for includes use of a professional tool that supports EDB to PST conversion and handles Exchange database corruption efficiently. Such tools not just make the corrupt EDB files accessible but also allow accessing deleted mailboxes and emails from the EDB files. It enables you to repair EDB files, regardless of the cause, and retrieve your data without any loss.
Conclusion
Errors like 0xFFFFFE02 JET_errLogWriteFail are troublesome for database admins. What you can do is check your EDB files by executing the ESEUTIL command and resolve the errors using an EDB backup file. If the backup is unavailable or your EDB is corrupt, use Kernel for Exchange Server recovery to quickly repair the corrupt EDB files or convert EDB to PST to recover emails. With this user-friendly Exchange Server data recovery tool, you can repair corrupt Exchange database.
Frequently asked questions
/r or /p? Ans. Before we know when to use these commands, let’s understand their meaning.
ESEUTIL /r: Soft recovery of database items
ESEUTIL /p: Hard recovery of database items
/r is used when you want to bring the database to a Clean Shutdown state from Dirty Shutdown. The method is safe and preserves integrity of mailboxes. However, /p is performed on a database infected with severe corruption. The method carries the risk of data loss.
Ans. Here are the causes behind the write operation failures within the transaction logs of Exchange Server:
1. Drive hosting the log files ran out of space.
2. Backups weren’t complete properly, restricting Exchange to delete old log files.
3. Existing transaction log file is corrupted or damaged.
