| Event Id | 4741 |
| Source | COM+ |
| Description | An attempt was made to access a SPM Property Group in LockMethod mode, by an object without JIT Activation, or by an object with a lock on another Property Group. Server Application ID:<ID> Server Application Instance ID:<ID> Server Application Name:<Name> The serious nature of this error has caused the process to terminate. Error Code =<Code>:There is no MTS object context COM+ Services Internals Information: File:<Location> Line: 127 Comsvcs.dll file version:<Version> |
| Event Information | According to Microsoft: CAUSE: This problem is caused because two property groups have been created with the isolation mode set to LockMethod. When you add a property to the second group, these errors are encountered. The reason for this is deadlock prevention. If component A in activity A creates a Group A with the isolation mode LockMethod, then component B in activity B creates group B with the isolation mode LockMethod. When component A now wants to access group B and component B wants to access group A, a deadlock occurs. Note that the isolation mode is set for the lifetime of the group. In other words, you cant create it with LockMethod and then access it with LockGetSet. RESOLUTION: When you use more than one property group per MTS or COM+ activity (method call from the COM+ or MTS perspective), you should use the LockGetSet method instead of the LockMethod isolation mode. You cannot create the first group with LockMethod and then create subsequent groups with LockGetSet, because you dont have control over the isolation mode once the group has been created. |
| Reference Links | PRB: Calling CreateSharedPropertyGroup with LockMethod in the Same Activity Causes Failfast |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.