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 an attribute length. Called from MTA. Procedure: 73. Database error code: ODXOINIU - Object does not exist. Object at fault: 06000034. Attribute identifier: 10. Value number: 1. Referenced object: 00000000 (00000000 => N/A). Referenced object error 0. [DB Server SUBMIT 14 72] (14)
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Exchange MTA Service?
If the Mtacheck utility is run against a database that was not shut down properly, Mtacheck deletes files that are greater than Db007fff.dat file, and when the MTA starts, it logs this event. See ME271600 for details on this issue.
See MSEX2KDB for additional information about this event.
As per Microsoft: "Customers who experience this problem on version 4.0 Exchange servers will need to upgrade to Exchange 5.5. Customers experiencing this problem on Exchange 5.0, will need to upgrade to Service Pack 2". See ME177887 and ME235534 for more details.
See ME828255 for a hotfix for Microsoft Exchange 2000 Server.
Woodrow Wayne Collins
See the "MTA Troubleshooting Guide" link.
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: ME177887, ME231685, ME235534, ME271600, ME828255, MTA Troubleshooting Guide, MSEX2KDB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated