"Cannot open log for source." Application not having access rights



I am trying to solve a problem that we have with our application not having
access rights writing to the event log.

An error occurred while invoking web service
"StartRequest@http://localhost/ApplicationX/WebServices/Handler.asmx"; using
network credentials "USER"

Reason:System.Web.Services.Protocols.SoapException: Server was unable to
process request. ---> System.InvalidOperationException: Cannot open log for
source 'ApplicationX'. You may not have write access. --->
System.ComponentModel.Win32Exception: Access is denied

--- End of inner exception stack trace ---

at System.Diagnostics.EventLog.OpenForWrite(String currentMachineName)



We usually solve the problem using this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323076

Adding (A;; 0x3;;;AU) in the access rights in the CustomSD normally solves
the problem as USER is a Authenticated User on the machine.

This time the problem is not being fixed.

After adding the value (A;; 0x3;;;AU) to the CustomSD the problem is solved
for a little while (1-2 hours), and the access right is being set to
(A;;CCDC;;;AU). After it has been set to this value the application is not
able to write to the eventlogsource.

I have also tried using this hotfix without having any luck:
http://support.microsoft.com/kb/939960

The server is a Windows Server 2003 not in a domain.

Any suggestions?

.



Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... error 15100 Win32 Error 15100. ... One is indicating it can't retrieve info about the System log. ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... (Event String (event log = Directory Service) ...
    (microsoft.public.windows.server.sbs)
  • Re: Server2003 2008 error !!
    ... Remove the x.x.1.x form the NIC of the DCs and configure it as a FORWARDER or use directly the ISPs DNS server as Forwarders in the DNS server properties in the DNS management console. ... On the 2008 make sure the internal firewall is not blocking AD replication, by default the firewall is enabled ion 2008. ... The event log File Replication Service on server ... EventID: 0x000003EE ...
    (microsoft.public.windows.server.active_directory)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... One is indicating it can't retrieve info about the System log. ...
    (microsoft.public.windows.server.sbs)