Makes me wonder what attribute 79 of object DB000035 is, and why the MTA
doesn't loop for attribute 79 of any of the other dat files.
State of Montana
Exchange FAQ: http://www.swinc.com/resource/exch_faq.htm
> Take a look at this MS KB article, it may help:
> You can also get this article by sending an E-mail with a subject of
> Chris Scharff, MVP-Exchange
> Senior Systems Consultant
> Simpler-Webb, Inc.
> Exchange FAQ: http://www.swinc.com/resource/exch_faq.htm
> E-Mail Resource Guide:
> >Sorry I forgot the event ID's
> >fatal MTA database server error was encountered. A bad list member length
> >on object 0600003F. File offset: 1177. Attribute ID: 79. Referenced
> >00000000 (0 => N/A). Referenced object error: 0. [DB Server DISP:ROUTER 9
> >42] (16)
> >An MTA database server error was encountered while reading an attribute.
> >Called from MTA. Procedure: 138. Database error code: 2111. Object at
> >0600003F. Attribute identifier: 79. Value number: 1. Referenced object:
> >00000000 (00000000 => N/A). Referenced object error 0. [DB Server
> >DISP:ROUTER 9 26] (14)
> >> Hi,
> >> We have a customer with a Exchange 5.5 SP3 server NT4 SP6a. 256MB RAM
> >> plenty of disk space (for now).
> >> It started about a week ago, the disks just filled right up and killed
> >> server. We fitted bigger disks and tried to restore, this was fine for
> >> a day then the disks started to loose space rapidly. To event errors
> >> recorded and Microsoft recommend running edbutil to rectify the
> >> of our engineers ran this and the server promptly died. We re installed
> >> and recovered the databases got the server back up and everything
> >> fine for a few hours then the same thing happened again.
> >> I'm going to see the server tomorrow and I don't really want to run
> >> again unless I have to, do you have any clues or recommendations?
> >> Thanks in advance.
> >> Andy.