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.
An MTA database server error was encountered while appending an attribute. Called from MTA. Procedure: 359. Database error code: ODXOINIU - Object does not exist. Object at fault: 06000034. Attribute identifier: 53. Value number: 1. Referenced object: 06000034 (00000000 => N/A). Referenced object error 2109. [DB Server SUBMIT 14 19] (14)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
As per Microsoft: "This event indicates that there was an internal error. This can happen if the message transfer agent (MTA) database is corrupt or the MTA DAT files are not accessible". See MSEX2K3DB for additional information about this event.
See ME157235 for information.
Elliott Fields Jr
This is caused by bad or corrupt .dat files (message) in the MTADATA directory. See ME231685 for details on correcting this issue.
|Private comment: Subscribers only. See example of private comment|
|Links: ME157235, ME231685, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated