Re: Service, Requested registry access is not allowed

Did you check regmon and filemon to see if there was an access denied error
generated like I suggested? This might help determine the root cause of the
problem.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"theking2" <theking2@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:578A9968-1561-491B-8EBF-D132165A2F2B@xxxxxxxxxxxxxxxx
I agree, Joe, it is not a great idea to elevate rights to circumvent access
rights issues. Therefor I had included an installer to setup the requered
eventlog assuming that the user installing the service has appropriate
rights. The service and eventlogs are installed still the service when ran
under "NetworkServices" throws the exception at the first WriteEntry which
also happens to be in the OnStart event.

The Key that defies opening is
"HKLM\SYSTEM\CurentControlSet\Services\EventLog\Security". Which is
performed
directly after accessing
"HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\Auto Recharge
Service".

I'm not sure what the eventLog instance does with the Security or
Application key as AutLog for the service is switch off (false). All code
related to setting up the eventlog instance is VS generated. Either this
generation is wrong (as in "contains a bug") the .NET Framework performs
some
incompatible updates or there is a setting I've overlooked.



.

Loading