| Event Id | 4194 |
| Source | COM+ |
| Description | "The description for Event ID ( 4194 ) in Source ( COM+ ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Component Prog ID: Server Application ID: Server Application Name: The serious nature of this error has caused the process to terminate. Exception: Address: Call Stack:" |
| Event Information | According to Microsoft: CAUSE: This problem occurs because a thread can be assigned to multiple activities in COM+ applications. This behavior causes excessive Message Queuing API calls in a relatively short time. If the thread is reentered while previous activity is blocked, the Mqrt.dll run time stops responding. WORKAROUND: To work around this problem, use one or both of the following methods. 1. Change the COM+ object behavior to use the EmulateMTSBehaviour registry subkey, and switch to the MTS model. The MTS behavior is one activity per single-threaded apartment (STA) thread. 2. Set the COM+ application to run while it is idle instead of closing. By default, the COM+ application closes after the application has been idle for three minutes or more. The application could stop responding when it restarts after closing. |
| Reference Links | FIX: An access violation may occur when the Message Queuing 2.0 run time (Mqrt.dll) is loaded in a COM+ application |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.