The primary responsibility of an administrator is to keep track of each and every symptom taking place in Exchange database. It is also equally important to have sound understanding of the causes of any issues and resolution. An Exchange database comprises huge data within its files, known as EDB. One of the Exchange issues is reflected when you are not able to mount the Exchange database in Exchange System Manager. Below is a full-fledge resolution to combat the problem. Let’s look.

You may come across an error stating

Operation terminated with error – 1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 388.645 seconds.

(Not to be confused with the time given in seconds; It changes.)

• First of all, you need to check the database state using ‘Eseutil /mh’ “path of database”.

• If you find the state as ‘Clean Shutdown’, all the files from Transaction logs folder are to be moved. Following, mount the stores. On the other hand, if the state is found as ‘Dirty Shutdown’, check whether the files addressed as ‘log required’ are available or not.

• Use the command ‘Eseutil /ml’ “Path of log fileslog prefix” to check if the required log files are in clean state.

• If log files are in clean state, use ‘Eseutil /r’ <Log Prefix> /l “Path of log files” /d “Path of database” to carry out the soft recovery.

• Once the operation is succeeded, mount the stores.

• However, after performing the soft recovery, you may encounter the following error:

• Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after n seconds.

• To deal with the error, use ‘Eseutil /i’ command. It will remove the EDB-STM mismatch.

• However, the other scenario includes missing or unclean log files necessitating either restoring from backup or performing hard recovery.

• When you use a software program to take the backup, it creates restore.env and logs at C:Temp location in a folder. Take a copy of this folder before performing the hard recovery.

• From the BIN folder in command prompt, use ‘Eseutil /cc’ “Path of restore.env that contains folder” command to perform hard recovery.

• Once the recovery is successful, you will find the restore.env and logs folder empty.

• If it’s been a few days when you took the backup and on completion, logs were created at production location, in this case, you need to ensure the availability of sequential logs (from the log in restore.env) in production location. If logs are not in sequence at production location, the command for hard recovery will fail to perform.

• You can avoid logs at production location using “eseutil /cc ‘restore.env folder path’ /t” command. However, you need to backup the folder again before you use the command.

• You can now mount the database.

Accidentally, you may fail to carry out the procedure properly. If so, use a professional Exchange recovery software application for getting access to the database.