ESEUtil (Extensible Storage Engine Utilities) is a command line tool that is associated with Microsoft Exchange database and log files. This inbuilt tool is generally used to verify, modify and repair Exchange database (EDB) files. Usually, it is used to repair a damaged or corrupted Exchange database and to restore data from a backup. This utility is located in the Exchange default install folder and in the Bin folder. ESEUtil can be used against any ESE database of Exchange Server 2010 or other versions.
However, many a times, this command itself becomes a cause of problem within the database. This happens due to incorrect execution of the command, version incompatibilities, or various other reasons.
This article describes Jet Error 1032 that occurs when the ESEUtil command fails. Read on to know about the reasons behind this error and how to resolve it.
In case, if it doesn’t help you, try out Exchange database repair tool:
ESEUtil Jet Error 1032
While trying to solve issues within the Exchange database by using the ESEUtil command, you may encounter the following error message:
“Exchange 2010 failed with Jet error 1032”
The error code 1032 usually occurs while trying to mount a recovery point. The complete event ID message in the application event log contains the following information associated with this error:
| Event Type | Error |
| Event Source | ESE |
| Event Category | General |
| Event ID | 490 |
| Date | Current Date |
| Time | Current Time |
| User | User with which you’re logged in |
| Computer | Server_Name |
The cryptic error name associated with Jet error 1032 is JET_ERRFileAccessDenied. It indicates that you do not have access to the file that you’re trying to use, it is locked or already being used by another program/user.
Reasons behind ESEUtil Jet Error 1032
ESEUtil jet error 1032 may occur:
- When you perform a ‘Replay Install’ but do not have the appropriate permissions assigned to the folder or the drive that contains the Exchange databases (i.e., the MDBDATA folder).
- When you run the ESEUtil command, while the database is mounted. The database needs to be offline so that the ESEUtil command can read the header information before attempting to repair it.
Common Fixes for Error 1032
This error can be resolved through the given manual fixes:
- Dismount the Exchange database and then try to run the ESEUtil command
- Run the Exchange Management Shell (EMS) on which you execute the ESEUtil command as the administrator.
- Open “services.msc” and stop all services related to exchange. Then run ESEUtil.
- Grant full permissions to the folder that contains the Exchange database and to the drive on which this folder exists. To grant full permissions, here are the steps:
- Open Windows Explorer and navigate to the folder that contains the Exchange database.
- Right-click on it and select Properties
- Click on the Security tab and then tick the following checkboxes:
- Administrators Full Control
- System Full Control
After the repair has been done, if you wish to revert the permissions back to default, follow the below mentioned procedure:
- Open Windows Explorer
- Right-click on the Local Disk object containing the Mailbox Database folder and select Properties.
- Click on the Security tab and then grant the default permissions:
- Administrators Full Control
- Creator / Owner None
- Everyone None
- System Full Control
- Users/ Read and Execute, List Folder Contents, Read
Limitations of Manual Methods
Though the above-mentioned manual fixes are free of cost and appear to be useful in most cases, they suffer from some limitations:
- After you fix the “exchange 2010 failed with jet error 1032” problem, further attempts to repair the database may fail.
- In some cases of serious database damage even the ESEUtil command fails to repair the database.
- Attempts to resolve error 1032 might result in severe damage to the database if not followed correctly.
Checking the .EDB file by running the eseutil command and using the /mh switch:
Repairing the .EDB file by running the eseutil command and using the /p switch:
Things to note before using the /P (Hard Recovery switch):
- There is no going back after executing the command. So, take a backup beforehand
- Microsoft will not provide support afterwards
- This option will purge anything that is damaged. So, you’ve to accept data loss
- There is no 100% guarantee that it will work and the database will mount
Recommended Solution
In order to overcome the limitations of manual methods and to make the process simpler, it is recommended to use a prominent third-party Exchange repair software. We suggest using Exchange Mailbox Recovery Tool. This competent software repairs corrupt EDB files and restores inaccessible mailboxes, with commendable accuracy and efficiency
Conclusion:
ESEUtil, the built-in utility provided by Microsoft, works most of the time. But in an event of a failure, you can rely on Stellar Repair for Exchange. The software can open the .EDB file no matter how damaged it is and then simply export it to PST files, which you can import later into the new Database by using PowerShell.
Video Testimonial By Microsoft MVP, Edward van Biljon
