
The last weeks of my internship are here and Martijn and I are testing our application for bugs and errors that we missed before. One of the things that's important for us is the import functionality of our application. Unfortunatly ASP.NET and IIS decided otherwise as the following error illustrates.
The following exception was thrown by the web event provider 'EventLogProvider' in the application '/Trainingportaal' (in an application lifetime a maximum of one exception will be logged per provider instance):
System.Web.HttpException: The EventLogWebEventProvider provider failed to log an event with the error code 0x800705DE.
at System.Web.Management.EventLogWebEventProvider.ProcessEvent(WebBaseEvent eventRaised)
at System.Web.Management.WebBaseEvent.RaiseInternal(WebBaseEvent eventRaised, ArrayList firingRuleInfos, Int32 index0, Int32 index1)
Something goes wrong during the import of a CSV file. The application show the correct error in the user interface, but it seems that ASP.NET lost its mind here during the process of logging the exception in the eventlog. If you are the administrator of the site, you probably have no idea what wend wrong.
Funny how .NET sometimes hides the true problem from developers.
2 comments
It is the d in the title, that went wrong…
🙂
Anonymous
I’m glad .NET doesn’t start throwing exceptions on that. It would make my life a lot harder ;P
willemm