none
Errors running ESEUTIL

    Question

  • Hello, I am trying to check on the health of my databases by running eseutil commands.  I get the same error below using /mh, or /ml, or /mk

    [PS] C:\>eseutil /mh "c:\program files\microsoft\exchange server\v14\mailbox\Mailbox Database 0103719849\Mailbox Databas e 0103719849.edb"

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

    Initiating FILE DUMP mode... Error: Access to source database 'c:\program files\microsoft\exchange server\v14\mailbox\Mailbox Database 0103719849\Mai lbox Database 0103719849.edb' failed with Jet error -1032. Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access file, the file is locked or in use) after 0.0 seconds.
    Tuesday, June 18, 2013 2:36 PM

Answers

  • Hi

    This behavior occurs due to missing log files or corrupt backup file. In both the cases, Exchange Server cannot access the source database and you face this issue.

    Please try the resolution on this link to see if it will work

    http://www.ms-exchange-server-recovery.com/blog/resolving-%E2%80%9Caccess-to-source-database-failed-with-jet-error%E2%80%9D-in-exchange-server

    You can try resolving this problem using Eseutil /p command line tool or by restoring the database again from backup. If possible, move unaffected files from problem database to new database.

    If the above method does not work, you need to repair and restore corrupt Exchange Server database using advanced and powerful third-party applications, known as Exchange recovery software.

    Cheers

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Zi Feng
    TechNet Community Support

    Saturday, June 22, 2013 3:55 AM
    Moderator

All replies

  • Hello

    The Database is dismounted ?

    Tuesday, June 18, 2013 4:07 PM
  • Hi,

    This happens with it mounted or dismounted.

    Steve

    Saturday, June 22, 2013 1:24 AM
  • Hi

    This behavior occurs due to missing log files or corrupt backup file. In both the cases, Exchange Server cannot access the source database and you face this issue.

    Please try the resolution on this link to see if it will work

    http://www.ms-exchange-server-recovery.com/blog/resolving-%E2%80%9Caccess-to-source-database-failed-with-jet-error%E2%80%9D-in-exchange-server

    You can try resolving this problem using Eseutil /p command line tool or by restoring the database again from backup. If possible, move unaffected files from problem database to new database.

    If the above method does not work, you need to repair and restore corrupt Exchange Server database using advanced and powerful third-party applications, known as Exchange recovery software.

    Cheers

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    Zi Feng
    TechNet Community Support

    Saturday, June 22, 2013 3:55 AM
    Moderator
  • Hi! Did you try "run EMS as administrator"? If UAС is turned on. In my case it work!!
    Thursday, August 28, 2014 4:31 PM