Re: e00.log

Hi,
If you don't have a backup, then you might have to do a hard repair of the
database
Steps :
- Disabled antivirus to avoid the scanning
- enable file level antivirus exclusion  KB artical :328841
- run eseutil/p on the databases
- run eseutil/d on the databases.
- rename the mdbdata to mdbdata.old
- create new mdbdata folder
- start the IS
- stop IS
- copy the database from mdbdata.old to mdbdata
- started IS
- isinteg -fix -s <server name> -test alltests
- mounted the database.
- deleted mdbdata.old
-- 
Cornelius Clay Ferreira
Microsoft PSS

"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."


"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
>