none
The database files in this storage is inconsistent RRS feed

  • Question

  • Hi… after a crash of the server (win2000, exch2000) we've copy the Mdbdata  in another PC. Reinstalled Windows 2000 Server and Exchange 2000 Server. Now we're trying to mount the mailbox store (Priv1.edb 5 GB) but we receive this error: The database files in this storage is inconsistent. So, following the MS article n. 327156: Eseutil.exe says that we have a "Dirty shutdown" database "Eseutil /p" remains in "stand by" on "repair damaged database" step at 90% (the day after was still at 90%). Any suggestion will be  very appreciated.... Thanks in advanсe to everybody.

    Monday, May 16, 2016 3:19 PM

Answers

  • Have just spent most of this week getting our e2k server up and running again. What about backups? We spent 2 days running eseutil /p and isinteg - finally got the information stores mounted but found approx 50% of users had absolutely nothing in their accounts. Then resorted to restoring from backup (we used MS backup)- was surprisingly straightforward and hassle free. If you haven't backups and eseutil /p will not run you will need to try a eseutil /r to get the databases into a 'consistent' or clean shutdown state before it will let you run the /p option. Our database was 12Gb and the /p took 8 hours to run. As a fallback you can try to use another tool like Exchange Server Recovery Toolbox. Here is the link http://www.oemailrecovery.com/exchange_server_recovery.html

    • Marked as answer by AdamHruska Friday, May 27, 2016 2:21 PM
    Friday, May 27, 2016 2:11 PM

All replies

  • Correct me if I am wrong, this is not a VB.NET project (this forum is for VB.NET only). Please clarify.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.
    VB Forums - moderator
    profile for Karen Payne on Stack Exchange, a network of free, community-driven Q&A sites

    Monday, May 16, 2016 3:35 PM
  • Hi,

    Since Exchange 2000 has been out of support, please try to upgrade to latest Exchange version.

    For your question, do your run below command to check the status of database:

    eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_name.edb"

    Moreover, please rerun above command to check status after run "eseutil /p" to restore mailbox store.

    If it display "Clean Shutdown", please go to your logs folder and rename the file E00.log.
    Then try to mound mailbox for testing.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Allen Wang
    TechNet Community Support

    Wednesday, May 18, 2016 2:29 AM
    Moderator
  • Have just spent most of this week getting our e2k server up and running again. What about backups? We spent 2 days running eseutil /p and isinteg - finally got the information stores mounted but found approx 50% of users had absolutely nothing in their accounts. Then resorted to restoring from backup (we used MS backup)- was surprisingly straightforward and hassle free. If you haven't backups and eseutil /p will not run you will need to try a eseutil /r to get the databases into a 'consistent' or clean shutdown state before it will let you run the /p option. Our database was 12Gb and the /p took 8 hours to run. As a fallback you can try to use another tool like Exchange Server Recovery Toolbox. Here is the link http://www.oemailrecovery.com/exchange_server_recovery.html

    • Marked as answer by AdamHruska Friday, May 27, 2016 2:21 PM
    Friday, May 27, 2016 2:11 PM
  • After that you'll need to do an isinteg - but be aware there can be significant data loss. Good luck.

    http://www.fixya.com/support/t25426221-restore_emails_from_edb_file

    Friday, May 27, 2016 2:11 PM
  • Thank you guys for your feedback and help. Sorry, that long time did not respond. This is because the issue was solved and I forgot to tell.) Thank you!
    Friday, May 27, 2016 2:22 PM
  • I'd say not. You are running two unsupported entities - Windows 2000 and Exchange 2000. Neither have been supported for years.

    If you call in for support, do not be surprised if it is refused.  You have advised your management of this, and that your are missing years worth or critical security updates?  Who accepted this risk?

    Not the message you want, but you need to address this before you get comprimised or have irrevocable dataloss. 

    If you cannot maintain Exchange on-premises as you are meant to, then look at Office 365.....


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Friday, June 3, 2016 1:44 PM