ESE Error 474 and ESE warning 705 AGAIN!!!

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Lewej - 12 Jan 2005 09:03 GMT

Hi
I have:
ESE error 474 Database Cache Error
ESE warning 705 Onlin defrag failed

I have had these before and managed to 'cure' by exporting mailboxes to .pst
and restoring. Now after just one month it has re-occurred.

Microsoft indicate that the problems are the result of a hardware error.
However I have run hardware diagnostics on the machine (Dell PE2400), and
have checked all the firmware with Dell. Dell basially say there is nothing
wrong with the machine or it's firmware.

Has anyone any suggestions as to the best method to proceed? I think it is
maybe a software issue rather than hardware, but cannot offer any useful data
to support thks.

Any ideas - TIA

Lewej

Reply to this Message

Martin Chisholm [MSFT] - 14 Jan 2005 19:34 GMT

Could you please post the entire message? Without knowing the exact
error, we'd just be speculating.

-martin

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

>Hi
>I have:
[quoted text clipped - 16 lines]
>
>Lewej

Reply to this Message

Lewej - 18 Jan 2005 08:29 GMT

Hi MArtin

Error's as follows:

Event Type:    Error
Event Source:    ESE
Event Category:    Database Page Cache
Event ID:    474
Date:        12/01/2005
Time:        00:05:48
User:        N/A
Computer:    JAVANT01
Description:
Information Store (3236) The database page read from the file "D:\Program
Files\Exchsrvr\MDBDATA\priv1.edb" at offset 1984401408 (0x0000000076479000)
for 4096 (0x00001000) bytes failed verification due to a page checksum
mismatch. The expected checksum was 1655116478 (0x62a712be) and the actual
checksum was 649948792 (0x26bd6e78). The read operation will fail with error
-1018 (0xfffffc06). If this condition persists then please restore the
database from a previous backup.

For more information, click http://www.microsoft.com/contentredirect.asp.

Event Type:    Warning
Event Source:    ESE
Event Category:    Online Defragmentation
Event ID:    705
Date:        12/01/2005
Time:        00:05:48
User:        N/A
Computer:    JAVANT01
Description:
Information Store (3236) Online defragmentation of database 'D:\Program
Files\Exchsrvr\MDBDATA\priv1.edb' terminated prematurely after encountering
unexpected error -1018. The next time online defragmentation is started on
this database, it will resume from the point of interruption.

For more information, click http://www.microsoft.com/contentredirect.asp.

Thyanks for looking a tthis

Cheers

Lewej

> Could you please post the entire message? Without knowing the exact
> error, we'd just be speculating.
[quoted text clipped - 24 lines]
> >
> >Lewej

Reply to this Message

Martin Chisholm [MSFT] - 19 Jan 2005 08:56 GMT

Sorry, I should have looked more at the event number. Yes, a -1018 is
usually a hardware problem.

Please look at KB 314917 (Hmmm, looks like it needs to be updated for
2003 SP1 and the new ECC checksums...).

The hardware problem may be with the computer, SCSI controller,
cabling, hard drives, memory, etc. In your case the checksum is
dramatically different, so the storage system is more likely than bad
memory.

In addition to hardware, it could be the fault of a bad driver (disk,
anti-virus, etc.). Drivers can trample on other processes' memory.

But the fact still remains: most of the time -1018 errors are from bad
hardware.

-martin

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

>Hi MArtin
>
[quoted text clipped - 69 lines]
>> >
>> >Lewej

Reply to this Message

Lewej - 19 Jan 2005 09:31 GMT

Hi MArtin

OK - thanks.

Lewej

> Sorry, I should have looked more at the event number. Yes, a -1018 is
> usually a hardware problem.
[quoted text clipped - 91 lines]
> >> >
> >> >Lewej

Reply to this Message

D. Gabriel - 18 Jul 2008 06:35 GMT

I'm getting the same batch of errors.. on brand new hardware that was
purchased specifically from the exchange 2007/server 2008 compatability list.
I've also updated drivers and firmware and contacted the manufacturer more
times than I care to remember to ask for help on this matter.

Considering the lack of stability in any other portion of the exchange
software, I find it hard to believe that I've got faulty hardware...

> Hi MArtin
>
[quoted text clipped - 97 lines]
> > >> >
> > >> >Lewej

Reply to this Message