I am writing an application which uses some .NET remote components that are hosted in IIS on a Windows 2003 Server.
When the remote component throws an exception, the exception information should be written to the EventLog on the Windows 2003 Server; however, Win2k3 seems to be a bit restrictive when a component that is hosted in IIS wants to write to the eventlog.
Although the component does not run under the IIS_WPG or ASPNET account (I am using Windows Impersonation), I always received the following exception when the .NET remote component wanted to write something to the eventlog:
You can get rid of this behaviour and make sure that the error is indeed written to the EventLog by following the steps below:
- Open the registry on the Win2k3 server using regedit
- Locate the
- Find the CustomSD key and append the following string to the existing value:
Now, the (impersonated) remote component should have rights to write to the EventLog.
Now, what is the meaning of the string you've just added to the CustomSD key ?