ESEUTIL /d error

[Tim Cooper]

I have just been brought into a company who have managed to acrue a 20GB
Private information store. I scheduled some down time this weekend to run
ESEUTIL /d on it to prune it a bit. However when I run the process about 30%
of the way through it drops out with the following error :-

Operation terminated with error 1526c Jet_errLVCorrupted, corruption
encountered in long-value tree).

I have been running through the isinteg tests since trying to find the
problem, but so far no luck :(

Anyone got any suggestions?

I am loath to run eseutil /p as I dont really want to loose any information
and the private information store will work fine.

Is this my only hope?

[Ben Smith]

Here is a technet that has alot of informations about the error that you
have...

http://support.microsoft.com/support/kb/articles/Q195/8/56.ASP

Ben Smith, MCSE

Tim Cooper <tim.c...@vwfs.co.uk> wrote in message
news:OXFQ7IJ0#GA.302@cppssbbsa04...

[Kevin Holman]

You do have 20GB of free space, yes?

--
These sites help:
http://www.swinc.com/resource/exch_faq.htm
http://www.ntfaq.com/exchange.html

--
Ben Smith wrote in message ...

[Tim Cooper]

Thanks for the info I am trying it as we speak :)

As for the 20GB spare unfortunately no, but I can use the /t with a network
map to another server where there is plenty of space.

Cheers

TC

[Rich Matheisen]

"Tim Cooper" <tim.c...@vwfs.co.uk> wrote:

>I have just been brought into a company who have managed to acrue a 20GB
>Private information store. I scheduled some down time this weekend to run
>ESEUTIL /d on it to prune it a bit. However when I run the process about 30%
>of the way through it drops out with the following error :-
>
>Operation terminated with error 1526c Jet_errLVCorrupted, corruption
>encountered in long-value tree).
>
>I have been running through the isinteg tests since trying to find the
>problem, but so far no luck :(

ISINTEG won't help fix a damaged LV.

>Anyone got any suggestions?
>
>I am loath to run eseutil /p as I dont really want to loose any information
>and the private information store will work fine.
>
>Is this my only hope?

If the database is otherwise in good shape you won't lose any
information by repairing it. You don't say what SP you're running, but
that LV problem was corrected in SP1. The SP won't fix already damaged
LV's though.

------------------
Rich Matheisen
MCSE, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm

[Tim Cooper]

I have just managed to repair the problem with eseutil /p and applying the
eseutils patch that is in the knowledge base article

http://support.microsoft.com/support/kb/articles/Q195/8/56.ASP

Thanks for all the help, much appreciated :)

Rich Matheisen <r.mat...@worldnet.att.net.NOSPAM.COM> wrote in message
news:379a2d84...@msnews.microsoft.com...