Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A fatal MTA database server error was encountered. A bad list member length is on object 06000035. File offset: 2004. Attribute ID: 79. Referenced object 00000000 (0 => N/A). Referenced object error: 0. [DB Server DISP:ROUTER 13 42] (16)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
Apply the latest service pack. Don't stop any services before updating. See ME166402 for more details.
Elliott Fields Jr
When this error occurs, the MTA stops responding because a bad message is being processed on the affected server. If you run MTACHECK, it reports no errors. Each time the MTA is restarted, the same error occurs with a different object (06######) referenced each time. This is caused by bad or corrupt .dat files (message) in the MTADATA directory. See ME159166 for details on correcting this issue.
|Private comment: Subscribers only. See example of private comment|
|Links: ME159166, ME166402, ME193049, ME253718|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated