Re: Security Log Warning
Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance
Try renaming the security log file manually. It could be corrupted.
C:\WINDOWS\System32\config\SecEvent.Evt
--
Jabez Gan [MVP]
Microsoft MVP: Windows Server
http://www.blizhosting.com
MSBLOG:
http://msblog.resdev.net
"KWME" <KWME@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2740ADD5-615D-492C-A164-2083A3BA82B1@xxxxxxxxxxxxxxxx
I've been having troupble with my Security Log warning. Whenever I log-on
to
my Server 2003 machine I get a "Security Log Full" warning. I've set the
log
to overwrite old logs, even to stop logging all together, but it still
coughs
up that warning every time. Any ideas?
.
Relevant Pages
- AuthzReportSecurityEvent
... I am trying to report Audit Events from our application into the Security Log ... on Windows Server 2003 using the AuthzReportSecurityEvent Security API. ... (microsoft.public.platformsdk.security) - Using AuthzReportSecurityEvent
... I am trying to report Audit Events from our application into the Security Log ... on Windows Server 2003 using the AuthzReportSecurityEvent Security API. ... (microsoft.public.platformsdk.security) - Re: sequrity eventLog
... Hope this was clearer to you now when I said it's not possible to write to the sequrity event log. ... If you want to write an event to the security log, you can use a new set of functions that was introduced in Windows 2003 (also available for windows server 2000 when you install the Authorization Manager Runtime). ... but till today I really thought that writing to the security log should be possible if you have the correct set of rights. ... (microsoft.public.dotnet.languages.csharp) - how to allow a user access to our server event logs?
... We want to setup a user on our domain with access to our Windows Server 2003 event logs, specifically the security log. ... (microsoft.public.windows.server.general) - Re: KSecDD - Login Process
... www.ilopia.com - FAQ and Tutorials for Windows Server 2003 ... "Mike" wrote in message ... > I am checking my Security log on my NT box and I cam across the following: ... (microsoft.public.windows.server.general) |
|