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.
|Source: Transaction Server|
An object call caused an exception. <additional information about which object caused the exception> (Microsoft Transaction Server Internals Information: File: <file name and line number>) (Exception: <exception code>)
(Address: <memory address>)
<function call stack>
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Transaction Server service?
As per ME291365, MTS and COM+ log this error because a component method caused an unhandled exception. The additional information may include some combination of the ProgID, CLSID, package name, interface name, interface ID (IID), and a number of the method that caused the unhandled exception. The exception code indicates what type of exception occurred. Common exception codes are c0000005 for an Access Violation or c0000094 for Division by Zero.
ME262187 provides information on interpreting Microsoft Transaction Server Events. The 4104 error indicates that the component DLL performed an illegal operation while creating an object.
For specific applications see ME267993, ME228495
|Private comment: Subscribers only. See example of private comment|
|Links: ME291365, ME262187, ME267993, ME228495|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated