• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 243
  • Last Modified:

Exchange DB mounting issue

Hello experts,

I have an Exchange 2010 SP1 DB> Accidentally deleted log files (as many other people did).

I have googled for tens of solutions but no one worked.

I tried to move all the rest of log files to a new folder.
I tried eseutil /mh and found that it's in dirty shutdown mode.
When trying to eseutil /p it gives error 1032 that file is locked or in use
I have shutdown all exchange services and still the same.
I used a file locking explorer utility to see if any other process is locking the file, but didn't find any thing locking.

Any help????
0
Muhajreen
Asked:
Muhajreen
  • 3
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
Something is locking it - I would say probably antivirus. Stop and disable the Exchange services, plus the AV services and then reboot the server. That will release the locks on the file.

Once you have the database mounted you should update your server. Exchange 2010 SP1 is no longer supported - you should update to SP3 with the latest rollup.

Simon.
0
 
MuhajreenAuthor Commented:
Thank you.

Ok I will disable all AV and exchange services and will reboot the server. Right now I am copying the deb file away to another server. I will update you shortly.
0
 
MuhajreenAuthor Commented:
After doing all the needful, disabling all exchange services and AV services, and after rebooting the server, again getting the same error 1032 when I try to run eseutil.exe /p "mailbox file"
0
 
Seth SimmonsSr. Systems AdministratorCommented:
i would use handle to see what has the file open

run this from elevated command prompt and redirect the output to a file then you can open in notepad (or other text editor) and search for the database file name.  then you scroll up to where it shows the process that has the file open and go from there.  let us know what that process is if you can't determine how to resolve at that point

Handle
http://technet.microsoft.com/en-us/sysinternals/bb896655

you would basically do handle > c:\handle.txt
0
 
MuhajreenAuthor Commented:
While services were still disabled, I ran EMS as an administrator, and that solved the problem.

I didn't formerly use to run EMS as administrator to give it authority to perform commands. This was strange. And no online article mentioned that (at least those which I was googling)

Thank you all for your kind support.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now