| Event Id | 0 |
| Source | Enterprise Instrumentation |
| Description | Error loading an Event Sink of type | Microsoft.ApplicationBlocks.Logging.EventSinks.LogEventSink, | Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.1, | Culture=neutral, PublicKeyToken=bde98c9c96b31b0d. The Event Source of | name Application will not write events out to this Event Sink. The | following exception was returned during the load: |
| Event Information | Youll need to install util to your instrumented assemblies. Normally you add a ProjectInstaller to your instrumented application and then run install util on it - this creates the EventSource in the Windows Event Log. (If this doesnt happen, the logEventSink will try and do it when, it is created - in this case there is insufficient permissions and it fails). Here you could add the ProjectInstaller to the instrumented assembly and run installutil on it. Here is some description of the installers in EIF below There are actually three installutils in EIF: 1) installutil-ing the instrumented app 2) installutil-ing the schema dll. 3) some installutil-ing goes on when you first install EIF. 1) installutil-ing the instrumented app: Yes, you can handcraft the EI.config file and not perform the installutil on the instrumented application. The only action missing would be the registration of the EventSources in the Windows Event Log (specifically no calls to System.Diagnostics.EventLog.CreateEventSource() are made).</p> <p>It should be noted that the LogEventSink will automatically call EventLog.CreateEventSource() if needed when the instrumented application is executed. The only problem is that sometimes apps (e.g. ASP.NET Web Apps) dont have sufficient permissions to make this call. In this case, the logEventSink fails to load for this EventSource, an error is output to the Windows Event Log (notifiying of the error) and events that would have been generated output to the logEventSink are dropped. 2) installutil-ing the schema dll.: This second one performs the following actions: a) checks that all the event Types are of valid structure (e.g. EIF doesnt allow self reference cycles - such as a typical node in a linked list structure) b) delegates through to WMI.NETs System.Management.Instrumentati |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.