Once again me, I could trace down my problem to some new
features within web.config (at least they didn't bother me in beta2).
There is a new entry in web.config
have a look if this might fix your problem
also have a look at this:
On Wed, 30 Jan 2002 09:02:06 +0100, Andreas K. Palm
>I do have the same problem, just brought over code I developed in
>beta2 to RTM and now I have this security exception, I think MS
>changed the concept here a bit ?!
>>That sounds an awful lot like an article that is available on
>>www.gotdotnet.com. The problem is I don't know exactly what key I need to
>>create in the registry, and the article doesn't have any more information
>>about how to go about creating the key at installation. Do I need to go to
>>the trouble of writing a program to run during installation that does
>>nothing but create the category, or is there some documentation about what I
>>need to put in the key so I can do it directly with a .reg file or
>>> The following information is from a "yet to be published" article...
>>> "Using the Event Log:
>>> Applications that need to write to the Application event log can do so
>>> running as the ASPNET account. If an application needs to create a new
>>> event log
>>> category, it must create a registry key under the HKLM hive, which the
>>> account cannot do. If impersonation is enabled and a privileged account is
>>> impersonated, the category can be created at run time. Otherwise, an
>>> administrator can create the category and the application can write to it
>>> at run
>>> Applications that need to create new event log categories should create
>>> categories at installation. Once the category is created, the ASPNET
>>> account can
>>> write to the log."
>>> If you need more information about this please let me know...
>>> Quentin Hurd
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> You assume all risk for your use. ? 2001 Microsoft Corporation. All rights