The COM+ Event System could not fire an EventObjectChange event to subscription %2 because a bad HRESULT was detected during filtering. The HRESULT was %1.%0
The COM Server with CLSID %1 and name "%2" cannot be started on machine "%3". Most likely the CPU is under heavy load. Error: ...
The COM sub system is suppressing duplicate event log entries for a duration of %1 seconds. The suppression timeout can be ...
The COM+ Event System caught an access violation at address %1 within method %3 of interface %4. The method attempted to ...
The COM+ Event System could not apply the filter criteria to subscription %2 with display name "%6" because the criteria ...
The COM+ Event System could not fire an EventObjectChange event to subscription %2 because a bad HRESULT was detected during ...
The COM+ Event System could not fire an EventObjectChange event to subscription %2 because the query criteria string "%3" ...
The COM+ Event System could not remove the %2 object %3.%rObject name: %4%rObject description: %5%rThe HRESULT was %1.%0 ...
The COM+ Event System could not store the per-user subscription %2 because the registry key HKEY_USERS\%3 could not be opened. ...
The COM+ Event System detected a bad return code during its internal processing. HRESULT was %3 from line %2 of %1. This ...