Corrupt Mailbox

Status
Not open for further replies.

zilantyas

Baseband Member
Messages
76
I'm using Exchange 5.5 I have a client with a corrupt mailbox. I ran a scan on the client machine and server. Fixed the errors on the client machine, but shortly after I did a scan again and the errors returned. This has given me reason to believe that the server is hosting the errors. I like to know if anyone knows of a way to repair just a user mailbox without repairing the entire Information Store. Is there an easy fix to this or is there any tools available that would simplfier and assist with this issue?
Thanks for all your help!

p.s. I've already tried to import .pst files so that I can delete the mailbox and re-create it but when importing the files it crashed on me and would not allow me to do so. Could this mean I actually do have a corrupt information store? Any help would be greatly appreciated. Thanks.
 
Hopefully the whole database won't be corrupted.

Have you tried eseutil.exe ??

Eseutil isn't the most accurate when it comes to displaying progress of the running process. Sometimes it can show 0% complete, then zoom to 99% and stay there for hours. It can take several hours to complete.

Did you run eseutil -g to check the integrity of the database?
Did you try Isinteg -fix -test alltests?

If your hard repair (/p) finally completes, you must run a /d before putting it back into production. Never put a /p database back into production without a /d. By doing so will cause performance problems on the server, latency for your users. Your users may also experience errors when trying to move or delete items too.
 
Status
Not open for further replies.
Back
Top Bottom