Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 496
  • Last Modified:

eseutil /p doesn't make it past the first scan, abruptly quits on dirty priv1.edb.

i've got a private store db that is dirty and needs to be repaired.  however, eseutil /p abruptly quits during the first scan pass.  the eseutil process uses up a considerable amount of ram (as shown in the task manager) prior to quiting.  the priv1.edb file size is 3.75Gb.  i've got 65Gb of free disk and 2Gb of ram to work with.  i'm just guessing that this might have something to do with ram and disk space.
0
stephenrbrown
Asked:
stephenrbrown
1 Solution
 
BNettles73Commented:


From first glance, I'd say you have plenty of disk space and 2GB should be enough ram. One of the best articles I've read about repairing exchange db's is here, "Repairing Exchange databases with ESEUTIL - when and how? " http://blogs.msdn.com/exchange/archive/2004/06/18/159413.aspx

Are you creating the temp db with the /t switch ... and are you trying to use the temp db over the network or keeping it local? Read through the article and let me know what you think.

You may want to copy the exchange db and log files to a safe place and then run an offline defrag with /d ....

That being said ... make sure you get a good backup before doing anything!
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

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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