asked on

Exchange 2010 Database won't mount. ESEUTIL error 1032

Hello-
We've got a machine that had a power failure and the Exchange Database won't mount after startup.
No matter what I do, I can't get ESEUTIL to address the database.

-I have tried running ESEUTIL /p, and I have tried both Command Prompt and Exchange Management Shell both running as Administrator.

I tried deleting the log files as well.
Below is the error I get when trying to run ESEUTIL.

[PS] C:\Windows\system32>eseutil /p "E:\Program Files\Microsoft\Exchange Server\Exchsvr\Mailbox Database 1258094299"

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.02
Copyright (C) Microsoft Corporation. All Rights Reserved.

Error: Access to source database 'E:\Program Files\Microsoft\Exchange Server\Exchsvr\Mailbox Database 1258094299' failed
with Jet error -1032.

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

Help would be greatly appreciated.
Thanks/

Skyler Kincaid

Try stopping the Exchange Information Store Service and then mounting the database. We have seen this error sometimes and stopping the service seems to fix it.

This error is caused when something is using the database and has a lock on it. Make sure AV or backup software isn't using the file.

Let us know how that goes!

slevin10

ASKER

Thanks, but unfortunately no luck. It's like some process has it locked but I can't figure out which one it is. I disabled all of the Exchange Services.
I also removed any AV, and there is no Backup Exec of backup software in play currently.

Skyler Kincaid

This program will be able to show you what program is locking the file:

http://www.emptyloop.com/unlocker/

Sajid Shaik M

check this

https://www.experts-exchange.com/questions/27442819/cannot-start-eseutil.html

and see the brief description about

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/eseutil-part1.html

all the best

ASKER CERTIFIED SOLUTION

slevin10

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

slevin10

ASKER

I ended up copying the database to an alternate location, and then running the repair on that database. (ESEUTIL /P) After that I moved it back to the original location and it worked from there.