MSExchangeIS application log errors
Nino Bilic
Few additional questions for you:
1. Your Exchange is actually running, right? When you reboot your Exchange,
the services do come up, is that right?
2. Did you maybe run a backup software or do you have an anti-virus software
that scanned Exchange files in the time when you got Event 145?
If you have file-level anti-virus software, definitely EXCLUDE Exchange
folders where you have your tatabases and logs.
Please post answers to those questions as depending on them, we can see what
you should do next.
Nino Bilic, MCSE+I
Microsoft Product Support Services
Microsoft Exchange
"Jon Leca" <jon....@amti.com> wrote in message
news:A6CQwCu1$GA....@CPMSFTNGSA04.privatenews.microsoft.com...
> We are running Exchange 5.5 (from Backoffice 4.5) SP3, on a NT Server SP5.
> 512 mb RAM.
>
> Yesterday afternoon, we received 2 application log events:
>
> 1) Event ID: 145 Source: ESE97 Type: Error
> MSExchangeIS (239) The database engine could not access the file called
> C:\ExchSrvr\MDBDATA\edb.chk
>
> 2) Event ID: 158 Source: ESE97 Type: Error
> MSExchangeIS (239) Unable to write a shadowed header for file
> C:\ExchSrvr\MDBDATA\edb.chk
>
> Circular Logging is enabled for both the DS and IS.
>
> If the database engine can't access the edb.chk file, how can the overall
> system know exactly which log transactions were posted to the database?
>
> This sounds like something I should worry about. What do you think?
>
> Thank you for your availability.
> You all are greatly appreciated.
> Jon Leca
>
>