Application fails to create custom eventlog on 2008 server even when run as admin

[DivyaNagarajan]

Hi,
I have a C++ Dll which only does logginG of data in to my custom log - say 'Log1'. This Dll is used by many vb.net dlls/applications for logging their corresponding data. All the applications and Dlls were earlier in .net 2003 and now migrated to 2010(Framework 4).
The custom log is not present in the system yet. SO my Dll has to create the log first befor adding the data and that is where it seems to fail.
This when tested on windows server 2008(Server also migrated from 2003 to 2008)throws a security exception.
The error reads as this - ' THE SOURCE WAS NOT FOUND.BUT SOME OR ALL EVENT LOGS COULD NOT BE SEARCHED.TO CREATE THE SOURCE,YOU NEED PERMISSION TO READ ALL EVENT LOGS TO MAKE SURE THE NAME IS UNIQUE. INACCESSIBLE LOGS : SECURITY'

[Banfa]

From StackOverflow

When you write the event log from any application, the event source needs to be already created, or the application itself will try to create it before writing to it. Unfortunately, creating an event source is an action which requires local admin priveledges.

So you can do two things:

pre-create the event source
make sure the user which your biztalk host is running as is in local admins (bad)

To pre-create the event source is a nicer option. You can do this via the powershell command

New-EventLog -LogName "Application" -Source "MyEsb"