Re: e00.log

As per Ex 2000, there are better methods to prevent database corruption.
Doing the last log rename schema MIGHT corrupt the database. The reson is
that operation that are logged in the missing log might already be
partally
in the database as well. Deleting the log will make the database not able
to
propery recover those operations.

Tjis is prevented in Ex 2000 BUT ... you will need to restore from backup.

--andrei
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"sccduck" <sccduck@[EMAIL PROTECTED]
> wrote in message
news:F7920F6A-22CF-45F0-9916-B92E71A5A83B@[EMAIL PROTECTED]
> Could you please help with the following?
>
> Symantec AV quarantined the E00.log file on our exchange 2000 server. 
The
file was not in the quarantine folder to restore.  Guided by a microsoft
article we renamed the last log file to e00.log and tried to resart the
IS.
This did not work.
>
> We then tried to run ESEUTIL /R /I /L /S as guided by  KB article
296843.
>
> The last event log entry was:
>
> Information Store (3168) Database recovery/restore failed with
unexpected
error 543.
>
> Can you offer any suggestions what to do next?
>
> Many Thanks
>
> Craig Shenton
>