Eseutil crashes out on repair of priv1.edb - Microsoft Exchange

Sometimes Antivirus scanners will quarantine the log files. Try
looking for them there.

Repair will create a text file like 'priv1.integ.raw'. You can open it
in notepad and see if the last few lines indicate anything strange
(admittedly it is very technical).

There were many bugfixes in `eseutil -p` for Exchange2003. It's
possible this has been fixed. But it is not safe to use the
Exchange2003 eseutil.exe and ese.dll on a database and then use that
database with Exchange2000.

-martin

Boring-but-necessary-disclaimer: This posting is provided "AS IS" with
no warranties, and confers no rights.


In article <45A6A283-4983-414F-BDD8-7B3040AC1EA7@microsoft.com>,
=?Utf-8?B?V2FsZG8=?= <Waldo@discussions.microsoft.com> wrote:
>I am running Ex2k Server with SP3. We experienced a problem with the
>information store when the server restarted and complained about missing
>logs. We tried to do a soft recovery using the logs but did not work. We
>only had a backup of about a week ago due to tape problems but restored it
>just to get everybody working again. I need to recover the data in the old
>privb1.edb (moved to temp location) but it keeps crashing out on about 40%
>without any error. The size of the priv1 is 4.2 GB and stm is 2.8GB. All
>the logs for the old priv1 is removed - I know you can repair without logs
>with some data loss which is fine. Is there any newer eseutil utility I can
>use or any way I can force the repair past the point where it stops?

You can use the Exchange 2003 SP1 version of eseutil.exe and ese.dll, but if
this completes you will need and Exchange 2003 server at the same build in
order to mount the store.



--
Tyrone Cowart
Microsoft

"Please do not send email directly to this alias. This alias is for
newsgroup purposes only."
"This posting is provided "AS IS" with no warranties, and confers no
rights."
"Waldo" <Waldo@discussions.microsoft.com> wrote in message
news:45A6A283-4983-414F-BDD8-7B3040AC1EA7@microsoft.com...
> I am running Ex2k Server with SP3. We experienced a problem with the
> information store when the server restarted and complained about missing
> logs. We tried to do a soft recovery using the logs but did not work. We
> only had a backup of about a week ago due to tape problems but restored it
> just to get everybody working again. I need to recover the data in the
old
> privb1.edb (moved to temp location) but it keeps crashing out on about 40%
> without any error. The size of the priv1 is 4.2 GB and stm is 2.8GB. All
> the logs for the old priv1 is removed - I know you can repair without logs
> with some data loss which is fine. Is there any newer eseutil utility I
can
> use or any way I can force the repair past the point where it stops?