Error access to source database failed with jet error 1032

Resolve Error: ESEUTIL Not Working to Fix Jet Error 1032

Eseutil (Known as Extensible Storage Engine Utilities) is a command line tool which is associated with Microsoft Exchange database and the corresponding log files. To verify, modify and repair the Exchange database file (EDB files) this inbuilt tool is used. This application helps in releasing corrupt Exchange EDB file of the server. The ESEUTIL tool helps in recovering both soft as well as hard deleted data from the database and is usually used on a damaged or corrupted Exchange database which restores data from the backup. However, there may be cases where ESEUTIL not working & causes trouble for users during its execution.

This ESEUTIL utility is located in the Exchange default install folder which is: Program FilesMicrosoftExchange ServerBin and can be used against any of the ESE database of Exchange Server 2010 or the earlier versions.
However, there are some limitations of this inbuilt tool due to which alternative techniques are undertaken. This command arises a problem within the database due to incorrect execution of the command, version incompatibilities issues etc, which can be reduced by taking some easy steps.

This article describes “ESEUTIL not working” error and the jet Error 1032 which occurs when the ESEUTIL command fails. Therefore, in this write-up we are going to discuss this issue and the need of other alternatives which are available.

Reasons behind ESEUtil /p not working ?

While attempting to resolve issues within the Exchange database, on running the ESEUtil command you may get the following error message:

“Exchange 2010 failed with Jet error 1032”

This Jet Error 1032 occurs when we try to mount a recovery point. The cryptic error name with this kind of error is JET_ERRFileAccessDenied which indicates that one has no access to the file that you’re trying to use or it has been locked or already being used by someone else or is being used by another program. This ESEutil Jet Error 1032 occur due to the following two reasons:

1. While performing a Replay install but one has no appropriate permissions assigned to the folder or the drive which contains the Exchange databases.

2. When you run the ESEUtil command while the DB is mounted. The database needs to be offline so that the command can read the header information before the attempting to repair it.

How to Fix the Error ESEUTIL Not Working 1032?

The error can be easily fixed by this manual method which is listed below:

1. First, dismount the Exchange database and try to run the ESEUtil command
2. Run the EMS (Exchange management shell) through which you can execute the ESEUtil command as an admin
3. Now, open “services.msc” and stop all the services related to Exchange, then run ESEUtil
4. You can now grant full permission to the folders that contains the Exchange database & the drive on which this folder exists.

To grant the full permission follow the steps:

1. Open Windows Explorer, navigate to the folder that contains Exchange database.
2. Right-click on it & then select the properties.
3. Click on the security tab and tick the checkboxes: Administrator full control & System Full Control.

The above-mentioned steps may help to fix the error ESEUTIL not working

Limitations of the Manual method

The above explained manual method can fix the error Eseutil /p not working free of cost and appear to be useful in most of the cases but suffer from some of the limitations which are:

Once you fix the “Exchange 2010 failed with jet error 1032” problem, then further attempt to repair the database may fail. In some serious scenarios where database is highly damaged even the ESEUtil command fails to repair or restore the database. While resolving error 1032 might result in severe damage to the DB if the steps to recover are not followed correctly.

What are the Alternative Solutions?

There are various alternatives available for the ESEUtil command which is used to repair EDB files, recover data from the corrupted files, and split Exchange EDB file. Thus in order to overcome the limitations of the above stated manual methods you can opt for simpler and recommend third party Exchange repair software. We will suggest you to use Exchange Recovery Tool by SysTools to recover exchange mailbox. This tool can quickly recover & repair dismounted offline Exchange database file in a hassle freeway without using any command.

Download Now Purchase Now

Note: In our opinion, the inbuilt commands like ESEUtil create a lot of major problems rather than curing issues within the databases. So, it will be good to avoid ESEUtil inbuilt feature if your database of Exchange is facing problems.

This advance utility provide scan mode option such as: Quick and Advance scan which recovers & repair corrupted dismounted / offline corrupted Exchange database file in a hassle freeway. To repair the minimally corrupted .edb file select the Quick scan and for the highly corrupted Exchange database choose advance scan. After recovery, users can easily export the recovered EDB mailboxes directly to the Live Exchange Server 2016/2013/2010/2007/2003 mailboxes, Office 365, and multiple file formats.

Also Read: Easy way to repair corrupted mailbox Exchange 2010 / 2013 / 2016

Many technical and non-technical users use this software as it provides an interactive graphical user interface which makes the users work easier and save their time as well as effort. It offers category option which allow users to export the selected Exchange mailbox data items such as: mails, notes, tasks, calendars, contacts, etc… to the desired export option. It support all version of Exchange Server & MS Outlook (2003 – 2016), and Windows OS version.

Conclusion

The above article read about ESEUtil command and the error “ESEUTIL not working” along with this the write up also explain the Jet error 1032 and the manual methods to repair Exchange database files using ESEUtil inbuilt utility. Further, you can also find the advance solution to recover Exchange files quickly with no compatibility issues.

In this Section, we find the solution of Exchange Eseutil error 1032, which in common in Exchange 2003/2007/2010 Server. We also discuss the various scenarios and different methods are available to fix jet error 1032 Exchange Server. Also, find the root cause of the problem and some tips that help Exchange user to avoid this kind issue. Some relevant queries are mentioned below related to jet error 1032 faced by 2003/2007/2010 Exchange user.

User Query Related to Exchange 2007/2003 Jet error 1032

Query 1: Getting message while running an operation in Exchange Server Database of 2003 “Operation Terminated – 1032 (JET_errFileAccessDenied, Cannot access file) and File is locked or in Use”.
Note: Trying to check the integrity of the Database using Eseutil Commands[/G]. A database should be mounted properly and no antivirus software installed in my system.
Any ideas to solve this Exchange error 1032.

Query 2: While restoring EDB File into clean shutdown state in Exchange 2007. When trying to run the command getting error “Operation terminated with error -1032 [Cannot access file, the file is locked or in use) after 20.93 seconds.] “. Remove the AV[ To check whether getting problem due to Anti Virus]. How Can I solve this problem? Please share any technique to fix Exchange 2007 eseutil error 1032.

Query 3: While working with Exchange Server 2010, had a Power failure and Exchange Database not mount properly. I tried ESEUTIL /p to fix the problem, and also use Exchange Management Shell but not the solution and get the error: Access to source database ‘E:Program FilesMicrosoftExchange ServerExchsvrMailbox Database 1258094299’ failed with Jet error -1032. Hoping for a good solution.

What is Exchange Eseutil 1032 Error?

As we can see in above user queries in different scenarios such as Dismounting, Shutdown process, running Exchange Commands, a user gets Exchange Eseutil 1032 error. Sometimes when a user tries to mount the database for recovery point for regular maintenance and get status “Suspended” and while exploring log files get error code 1032 and message: The file is locked or in use. —> Microsoft.Exchange.xx.xxFileAccessDeniedException: Cannot access the file, the file is locked or in use (-1032). To change the state from “Suspended ” to “Healthy” user need to know the exact reason behind the Jet error 1032.

Reason Behind Exchange Eseutil 1032 Jet Error?

Sometimes user ignores some prevention while working with EDB file and try to run command give by in-built Eseutil utility without knowing the actual cause of the problem. Naive user run Eseutil command without dismounting Exchange Server database. Sometimes a hardware failure or antivirus program can create this kind of error, even a corrupted database lead to this Jet error 1032 in 2003/2007/2010 Exchange Server. Some details of defrag error 1032 is given below:

Solution to Fix Jet error 1032 in Exchange 2003/2007/2010 Server

The main reason of Exchange error 1032 is that user doesn’t have permission to access the file and or file is already in locked state and already in use. To Fix this user can go for given approaches.

Approach 1: Disable Antivirus Application

Uninstall or Disable the Anti-Virus program in the configured system. An Antivirus program can disable the permission setting, that disallows to access the database and user get Jet 1032 error.

Approach 2: Run Eseutil Commands to Fix Exchange Server Eseutil Jet Error

If any EDB file is corrupted then a user can Open Exchange Management Shell and try to run Repair command using Full Administrator Mode.

To change the Permission mode follow steps:

• Go to Exchange Management Shell >> Run eseutil /p Command
• Now find the Folder store Database file >> Right Click on Database >> Select Properties.
• Select Security option and check System Full Control & Administrator Full Control.
• Now try to check the status of File. If the status changed to “Healthy” then you can access the database.

Alternative Solution to Fix Jet Error 1032

A manual solution does not always fix the problems even sometimes, without taking proper backup of the database file, a user can lose important information and sometimes not even to access the healthy database due to the damaged database file. To Fix Exchange Eseutil Jet error 1032 in 2010/2007/2003 Exchange Server, user can go for Exchange Mailbox Recovery Tool that can easily recover the damaged database file, that can help a user to access the desired database file.

Привет. Столкнулись с ситуацией – нежданно-негаданно отвалился Mailbox Database в Exchange 2010, из-за ошибок, указанных в заголовке. Хочу рассказать, что было в нашем случае, и как подобное можно решить.

Само собой сразу после того, как база отвалилась, попробовали её примонтировать, но безрезультатно, сразу после монтирования статус у базы снова становился Dismounted. Конечно, первым делом изучили логи. Обнаружили там занимательные записи:

Source: ExchangeStoreDB
ID: 206
Level: Error
Source: ExchangeStoreDB
Message: At ‘9/26/2012 8:48:36 PM’ database copy ‘DB’ on this server appears to have a serious I/O error. To help identify the specific failure, consult the Event log on the server for other storage and “ExchangeStoreDb” events. Service recovery was attempted by failover to another copy. Failover was unsuccessful in restoring the service. Error: Couldn’t perform the database failover.

Так же может встретится что-то вроде:

Source: ESE
Event ID: 739
Task Category: General
Level: Error
Description:
Information Store (5652) TestDB: The NTFS file attributes size for database ‘F:TestDBTestDB.EDB’ is 243136 bytes, which exceeds the threshold of 204800 bytes. The database file must be reseeded or restored from a copy or backup to prevent the database file from being unable to grow because of a file system limitation.

Проблема тут кроется не в самой базе, как таковой — база цела и невредима, а в файловой системе. Точнее в ее ограничениях. У каждого файла есть такой параметр, как Attribute List Size, так вот он не может быть больше 256КБ. И заполняется этот параметр тем быстрее, чем меньше установлен размер кластера на разделе, где находится база. Уменьшаться он не может. И когда он заполнится, база просто не сможет расти и будет отключена. Кроме того, есть еще такой параметр, как количество фрагментов для каждого файла, и этот параметр не может превышать примерно 1500000 фрагментов. Более подробно про данные штуки можно почитать тут и тут, по этому особо не буду останавливаться на теории. Скажу только, что данные ограничения связаны со скоростью работы дисков и принципами работы NTFS. Чем больше у вас будет фрагментов, тем дольше будут происходить операции ввода и вывода на диск. И вот если они приблизятся к указанным значениям, то нагрузка может стать критичной.

Как быть? Сперва необходимо убедиться, что проблема действительно связана с Attribute List Size или в количестве фрагментов.

Для этого можно выполнить команду:

eseutil /ms f:dataDB.edb

В выводе можно будет увидеть примерно следующее:

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode…
Error: Access to source database ‘f:dataDBName.edb’ failed with Jet error -1032.
File Information:
  File Name: f:dataDB.edb
  Volume Name: Drive2
  File System: NTFS
  Cluster Size: 4096 bytes
  Attribute List Size: 256 KB
  Extents Enumerated: 1157172

Если в выводе Attribute List Size меньше 256КБ или Extents Enumerated меньше примерно 1500000, то проблема у вас не вышеописанном. Если же что то совпадает, то это наш случай.

Для исправления ситуации бессмысленно делать дефрагментацию на диске и базе. Единственный способ – скопировать базу на другой диск, что бы все данные записались последовательно. Желательно сразу на раздел с рекомендованным размером кластеров, как минимум в 64КБ (кстати, это является рекомендацией Microsoft, для Exchange). После этого, если планируете оставить оригинальный диск его необходимо отформатировать с размером сектора 64КБ и скопировать базу обратно.

Форматирование делается командой:

 format F: /q /y /fs:ntfs  /v:VolumeName /a:64K 

Если вы не хотите перемещать базу на оригинальный диск, то указать путь до нового расположения Mailbox Database можно командой:

move-databasepath -identity DB -edbfilepath "путь_до_edb" -configurationonly

Как вы могли заметить в заголовке у меня указано 2 ошибки. После того как мы скопировали так базу, она успешно примонтировалась, но в логах обнаружилось следущее:

Source: MSExchangeIS Mailbox Sore.
Event ID: 9685
Exchange store ‘DB’: The current physical size of this database (the .edb file) is 1247 GB. This database has exceeded the size limit of 1024 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit.

Либо может быть зафиксировано аналогичное событие:

Event ID: 1216
The Exchange store DB is limited to 1024 GB. The current physical size of this
database (the .edb file) is <1 GB. If the physical size of this database minus its
logical free space exceeds the limit of 1024 GB, the database will be dismounted on a
regular basis.

При подобных событиях, база если и примонтируется, то, скорее всего, не на долго. В Exchange есть заданное ограничение на размер базы – 1ТБ, если база разрастется выше этого предела, то она просто будет отмонтирована. При достижении лимита может быть зафиксировано событие – 9690.

К счастью, этот лимит можно поднять до 2ТБ, возможно и до большего значения, но официально поддерживаются именно базы размером до 2 ТБ. Для этого:

Определим guid нашей базы:

Get-MailboxDatabase DB | fl guid

Дальше в реестре по пути HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISИмя_СервераPrivate-[ваш_guid] нужно создать параметр Dword, если его нет — «Database Size Limit in GB» и ввести нужное значение максимального размера.

Информация по второй проблеме взята отсюда.