RE: Cannot open log for source {0}. You may not have write access.
From: Magdelin (magdelinsuja_at_newsgroups.nospam)
Date: 08/25/04
- Previous message: Raterus: "Re: Return credentials with anonymous authentication?"
- In reply to: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Next in thread: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Reply: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 Aug 2004 08:55:02 -0700
Hi Luke,
Thanks for your reply. the SD (A;;0x0002;;;AU) worked when I added it to the
existing CustomSD value in
HKLM/CurrentControlSet/Services/EventLog/<CustomEventLog> key.
But, I have another problem on my web server regarding event logs. The web
application also writes to the custom event log on the web server. But unlike
the business component on the app server, web application is configured for
basic authentication and identity is NOT impersonated. The application pool
identity is set to NETWORK SERVICE account. The custom event log and event
source is registered on the web server.
The web application was successfully logging errors to the custom event log
on the web server with no additional privileges earlier. But, while
troubleshooting the error that occurred on the app server, I added read/write
privileges to the ASPNET a/c and N/W service a/c to the registry key
HKLM/CurrentControlSet/Services/EventLog/<CustomEventLog>. Later, I
discovered the problem was with the app server and removed the additional
privileges from the above mentioned key. Now, the I get a error "Registry
access denied" whenever the web app tries to log errors to the custom event
log. Now even if I re-grant read/write access to same the registry key the
"Registry access denied" error is repeated.
Any quick pointers will be greatly appreciated.
Thank you.
Magdelin
"[MSFT]" wrote:
> Hello ,
>
> For such a issue, you may goto to the following registry key:
>
> HKEY_LOCAL_MACHINE/System/CurrentControlSet/Application
>
> And locate the CustomSD key and add the following string to the existing
> value:
>
> (A;;0x0002;;;AU)
>
> A: SDDL_ACCESS_ALLOWED
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/se
> curity/ace_strings.asp
>
> 0x0002: ELF_LOGFILE_WRITE: Permission to write log files.
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/
> event_logging_security.asp
>
> AU: Authenticated Users
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/security/se
> curity/sid_strings.asp
>
> Here are some related articles:
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/
> event_logging_security.asp
> http://msdn.microsoft.com/library/en-us/dncode/html/secure06122003.asp
>
> Hope this help,
>
> Luke
>
>
>
>
>
- Previous message: Raterus: "Re: Return credentials with anonymous authentication?"
- In reply to: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Next in thread: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Reply: [MSFT]: "RE: Cannot open log for source {0}. You may not have write access."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|