Event ID 4106
| Event ID | 4106 |
| Source | EventSystem |
| Type | Warning |
| Description | The com+ Event System detected a corrupt IEventSubscription object. The COM+ Event System has removed object ID {<object ID>}. The subscriber will no longer be notified when the event occurs. |
| Comments and links for event id 4106 from source EventSystem | |
| Event ID | 4106 |
| Source | EventSystem |
| Type | Error |
| Description | The COM+ Event System failed to create an instance of the subscriber partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{6295DF2D-35EE-11D1-8707-00C04FD93327}. CoGetObject returned HRESULT 8000401A. |
| Comments and links for event id 4106 from source EventSystem | |
| Event ID | 4106 |
| Source | EventSystem |
| Type | Error |
| Description | The com+ Event System raised an unexpected access violation at address 0x7629E4D5, attempting to access address 0xFFFFFFE8. Please contact Microsoft Product Support Services to report this error. es!Ordinal3+0xe4d5 |
| Comments and links for event id 4106 from source EventSystem | |
| Event ID | 4106 |
| Source | MSDTC |
| Type | Error |
| Description | Could not install the MS DTC service. |
| Comments and links for event id 4106 from source MSDTC | |
| Event ID | 4106 |
| Source | MSExchangeIMC |
| Type | Error |
| Description | The dial-up connection <phonebook entry name here> could not be made. The error reported was: [87] The parameter is incorrect. |
| Comments and links for event id 4106 from source MSExchangeIMC | |
| Event ID | 4106 |
| Source | netflx3 |
| Type | Information |
| Description | Netelligent 10/100TX PCI UTP Controller #2 : Network link has been restored. |
| Comments and links for event id 4106 from source netflx3 | |
| Event ID | 4106 |
| Source | Otman4 |
| Type | Error |
| Description | Wrong version of the driver has been loaded on this system |
| Comments and links for event id 4106 from source Otman4 | |
|
Contribute If you have details about an event with id 4106 that is not listed in our database, please, send it to us. The submitted event will be forwarded to our consultants for analysis. We recommend you to check the EventID.Net Processing Queue to see if the event was already been submitted by another contributor. | |