General discussion

  • Creator
    Topic
  • #2290527

    Exchange 5.5 priv.edb corrupt

    Locked

    by mgosselin ·

    I have a client without backups, of course. Their priv.edb went down inconsistent – and i have run eseutil /p, and eseutil /r til my face is blue – to no avail. Anyone know of any other options/utilities to check into?

    Thanks for your help.

All Comments

  • Author
    Replies
    • #2710975

      Reply To: Exchange 5.5 priv.edb corrupt

      by dmiddltn ·

      In reply to Exchange 5.5 priv.edb corrupt

      Yep…
      This utility will extract as PSTs what’s in the EDB.
      http://www.officerecovery.com/exchangeserver/index.htm
      (It’s a little expensive, but it does work)

      You can also try this utility; but it’s mostly ment for a good EDB that you need stuff out of.
      http://www.ontrack.com/powercontrols/

      • #2711670

        Reply To: Exchange 5.5 priv.edb corrupt

        by mgosselin ·

        In reply to Reply To: Exchange 5.5 priv.edb corrupt

        thanks alot – we checked out the office recovery and although it takes FOREVER to get all the way through – it worked like a champ. recovered 95% of the data – only caveat, is that the recovered emails will not contain the actual email addresses, both to: and from: they will only show up as unknown@unknown.unk – and no contacts recovered.

        great help though – thanks a lot!!!

        Mike

    • #2711672

      Reply To: Exchange 5.5 priv.edb corrupt

      by tp205 ·

      In reply to Exchange 5.5 priv.edb corrupt

      The only other thing you can do is to move just the log files to a different directory and then run isinteg-fix this is a distructive rebuild but if you make a copy first of all the files then run it, if it crashes during it you can try again. REMEMBER: move all the log files out of the directory but keep Priv.edb and pub and ds in there.

    • #2711669

      Reply To: Exchange 5.5 priv.edb corrupt

      by mgosselin ·

      In reply to Exchange 5.5 priv.edb corrupt

      This question was closed by the author

Viewing 2 reply threads