Re: ASPNET can't write in event log on win XP

From: richlm (richlm_at_nospam.nospam)
Date: 01/18/05 

Date: Tue, 18 Jan 2005 10:00:32 +0100

see http://support.microsoft.com/default.aspx?scid=kb;en-us;842795

Yes the default registry permissions on XP/2003 are tighter than on 2000.

The first time your app tries to write to the event log, it checks to see if
an event source for your application (typically the application name)
already exists. If not, it tries to create it.

Event log sources are stored in the registry under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\...

Changing file system permissions will have no effect on the registry. If you
start regedit.exe and locate the registry key above, right click and select
'Permissions' you can see which accounts do have access.
You could just add the ASPNET account here, but this is a BAD idea because
it will complicate deployment of your application and weaken security.

The usual solution is to create the event source at installation time using
EventLog.CreateEventSource (or the EventLogInstaller class). Installation
will normally be done in the context of an administrator account.

Here's a couple of links to get you started:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbwlkWalkthroughCreatingEventLogInstallers.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskaddingyourapplicationassourceofeventlogentries.asp

Relevant Pages

  • Re: Win XP event log: Access denied
    ... Yes the default registry permissions on XP/2003 are tighter than on 2000. ... The first time your app tries to write to the event log, ... Event log sources are stored in the registry under: ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: security exception within Microsoft Application Block ExceptionManager.vb
    ... I am in the registry now. ... > ASPNET account doesn't have permission to create EventLog's, ... > Accessing the Event Log ... > not have sufficient permissions to create new event sources. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Security Exeception during upgrade
    ... You are absolutely right, it was user permissions. ... In order for the app to use the event log, ... open the registry with regedit, find the key for Event log and modify the ... >> level in the configuration file. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • What key to add in CurrentControlSetServicesEventlog???
    ... What do I add to the registry? ... in order for web apps to write to the event log, ... Go into 'regedit', go to the key above, set permissions for the specific ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Active Directory domain policy not available - Windows cannot access the registry information (5
    ... shuffling the registry around as a result. ... >What share permissions did you change? ... >SYSVOL and NETLOGON shares aren't accessible. ... >the domain controller is changed but the DNS still points to the old IP ...
    (microsoft.public.backoffice.smallbiz2000)