When using Paladin in a web application (ASP.NET), you may intermittently receive a System.Security.SecurityException from your application. You will discover that this error is raised from Paladin.Core.dll
The reason is because Paladin will attempt to create an Event Source in the Systems Event Log when an error has occured. It will write the error information to the EventLog in its own EventSource named Paladin. There error information contains diagnostic information that you can use to debug your application. They can be viewed using the Event Viewer.
However, when Paladin is deployed into ASP.NET, the ASPNET account does not have the rights to create a new Event Source. This will cause a System.Security.SecurityException to be thrown, blanketing the original error.
This PRB actually explains this. You may need to manually create an Event Source for Paladin
- or -
Write a simple Windows forms application using Paladin and purposely supplying it with an errorneous connection string. Run the Windows forms application with an administrative account and the Event Source should be created.
This problem does not affect Windows Forms applications. This problem may affect all versions of Paladin including the pre-release 0.9.0 version.
If you are not experiencing this problem in your ASP.NET application, please ignore this article.