[Resolved] Exchange 2010 ESEUtil Operation Terminated with Error 1032

admin | data recovery software Uncategorized | 4 minutes read | Modified on: 30-01-2020

MS Exchange Server provides in-built command line tool named Exchange Storage Engine Utilities (ESEUtil) to store and manage its database and log files. This tool is used to validate, amend and repair Exchange Server EDB files. It is generally used on corrupt or damaged Exchange database and for restoring data from backup. It can be used to repair and recover EDB database of Exchange Server 2010, 2007 and earlier editions. You can find the ESEUtil tool located at Exchange default installation folder :

<System Drive>:\Program Files\Microsoft\Exchange Server\Bin

Unfortunately, this ESEUtil command becomes the major cause of problem inside the database. It can happen due to incorrect commands execution, version incompatibilities etc. And normally, the effects of these problems can be fixed with some simple steps.

This write up will describe about JET Error 1032 that happens at the time of failure of ESEUtil command. Read the following section to know the reason for this error and various solutions to resolve it.

What is ESEUtil Jet Error 1032 ?

When you try to resolve Exchange Database issues with ESEUtil command, you may get the following message :

Exchange 2010 failed with Jet Error 1032

Generally, this error code appears when you try to mount the Exchange database recovery point. The complete event ID message, inside the application event log, consists of the following information related to this error:

The cryptic error name related to this Jet Error 1032 is JET_ERRFileAccessDenied. It usually indicates that either you don’t have access to the data file that you are trying to use or it is already in use by another program or it is locked.

Reasons for Occurrence of ESEUtil JET Error 1032

The “Exchange 2010 ESEUtil operation terminated with error 1032” occurs due to following reasons :

  • When you try to perform re-Install, but you don’t have appropriate permissions assigned to the drive or folder, which holds Exchange databases (i.e., the MDBDATA folder).
  • You run ESEUtil command when the Exchange database is mounted. This database needs to be set offline, in order to let ESEUtil command to read the header information before it attempts to repair or fix it.

How to Fix Exchange 2010 ESEUtil Operation Terminated with Error 1032

You can manually fix this error, as mentioned below :

  • First dismount Exchange database and then try running ESEUtil command
  • Run Exchange Management Shell (EMS) as administrator, for executing ESEUtil command.
  • Go to “services.msc” and stop all the services associated with MS Exchange. Now run ESEUtil command
  • Grant full permission rights to the folder containing Exchange database and to the Drive where this Exchange database folder is. Follow these steps to grant full permissions to the folder:
    • First Click on Windows Explorer to open it. Now browse the folder consisting of Exchange database.
    • Press Right-click >> Properties
    • On the Security tab, select the subsequent checkboxes:
      • Administrators Full Control
      • System Full Control

Once the Exchange database repairing process is done, you can revert all the permissions back to default. Follow these steps to do so :

  • Open Windows Explorer
  • Right-click Local Disk object which contains Mdbdata folder >> select Properties.
  • On Security tab, grant default permissions:
    • Administrators Full Control
    • System Full Control
    • Owner / Creator None
    • Everyone None
    • Users Read and Execute, List Folder Contents, Read

Problems with Manual Method

Although the manual methods are free of any charges and prove to be helpful in most cases, buy they have some limitations :

  • As you fix the “exchange 2010 failed with jet error 1032” problem, the further attempts for database repairing may fail.
  • In case of extremely damaged Exchange database, even ESEUtil command fails to fix it.
  • Attempts to manually resolve JET error 1032 might lead to severe damage to the Exchange database, if not done properly.

Screenshot showing checking of EDB file by executing the ESEUtil command and using /mh switch:

Screenshot showing repairing of EDB file with ESEUtil command and using /p switch:

Use Professional Utility – Recommended Solution

As you can see the above mentioned manual method is quite complex for non-technical users. So, if you want to completely avoid the limitations of manual methods and to make the entire EDB recovery process simpler, it is recommended that you go with a professional third party Exchange EDB Repair utility and easily resolve “Exchange 2010 ESEUtil operation terminated with error 1032” and related queries. EDB Recovery software is a prominent solution to fix and recover corrupt, dismounted, inaccessible, extremely damaged EDB database and restores it to healthy PST, EML, PDF, HTML, MBOX files with complete efficiency.

Conclusion

The in-built ESEUtil tool of Microsoft works completely fine when performing EDB repair process. But in case of its failure, you can bank upon EDB Recovery Tool that provides instant and precise solution for fixing and retrieving encrypted, corrupt, damaged, inaccessible EDB mailbox and exporting it to PST or directly into Live Server and Office 365 account. you can even try its FREE Demo edition that recovers complete EDB mailbox data, but saves only first 25 items per folder to required output format, as free trial.