Security Login Full

Anyone know why the security login keeps filling up in XP Pro. I clear it and
it keeps filling up (2 Days or so) for the user with limited rights.

Check the Event Viewer Log Size & Overwrite options.

Open the Event Viewer...
Start | Run | Type: eventvwr | Click OK |
Right click Application on the left | Click Properties |
On the general tab set Maximum log size to ?? KB |
Select Overwrite events older than XX days and set it to ??

Right click on the left | Click Properties |
On the general tab set Maximum log size to ?? KB |
Select Overwrite events older than XX days and set it to ??

Right click System on the left | Click Properties |
On the general tab set Maximum log size to ?? KB |
Select Overwrite events older than XX days and set it to ??

Maximum log size...
[[Provides a space for you to enter the maximum log file size. Or click the
arrows to change the log file size. The default maximum size is 512K.
The overwrite options on this tab specify what happens when this limit is
reached.]]

Overwrite events as needed...
[[Specifies whether all new events will be written to the log, even when the
log is full. When the log is full, each new event replaces the oldest
event.]]

Overwrite events older than XX days...
[[Specifies the number of days a log file will be retained before writing
over it. You can set the number of days before a log can be overwritten,
using numbers from 1 to 365. New events will not be added if the maximum log
size is reached and there are no events older than this period.
The default setting for this option is 7 days. This is the best choice if
you want to archive log files weekly.]]

Do not overwrite events (clear log manually)...
[[Specifies whether existing events will be retained when the log is full.
If the maximum log size is reached, new events are discarded.
This option requires that you manually clear the log. Select this option
only if you must retain all events.]]

The security log on this system is full. Only administrators can log on to
fix the problem.

"The security log on this system is full" message when you try to
log on to a computer that is running Windows XP or Windows
Server 2003
http://support.microsoft.com/kb/867860

How To Prevent Auditable Activities When Security Log Is Full
http://support.microsoft.com/kb/140058

STOP 0xC0000244 when security log full
http://support.microsoft.com/kb/232564

Users cannot access Web sites when the security event log is full
http://support.microsoft.com/kb/832981

RPC "Server is Unavailable" Message When Audit Log is Full
http://support.microsoft.com/kb/242361

The event log stops logging events before reaching the maximum log size
http://support.microsoft.com/kb/312571

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:69216102-6674-4E90-9F31-702F313AE97E@microsoft.com,
Surfingnewport <Surfingnewport@discussions.microsoft.com> hunted and pecked:
> Anyone know why the security login keeps filling up in XP Pro. I clear it
> and it keeps filling up (2 Days or so) for the user with limited rights.

I clear the security log which I have 512K of space available for it and an
overwrite when needed selected. Two days later its full again. Any idea whats
going on?

"Wesley Vogel" wrote:

> Check the Event Viewer Log Size & Overwrite options.
>
> Open the Event Viewer...
> Start | Run | Type: eventvwr | Click OK |
> Right click Application on the left | Click Properties |
> On the general tab set Maximum log size to ?? KB |
> Select Overwrite events older than XX days and set it to ??
>
> Right click on the left | Click Properties |
> On the general tab set Maximum log size to ?? KB |
> Select Overwrite events older than XX days and set it to ??
>
> Right click System on the left | Click Properties |
> On the general tab set Maximum log size to ?? KB |
> Select Overwrite events older than XX days and set it to ??
>
> Maximum log size...
> [[Provides a space for you to enter the maximum log file size. Or click the
> arrows to change the log file size. The default maximum size is 512K.
> The overwrite options on this tab specify what happens when this limit is
> reached.]]
>
> Overwrite events as needed...
> [[Specifies whether all new events will be written to the log, even when the
> log is full. When the log is full, each new event replaces the oldest
> event.]]
>
> Overwrite events older than XX days...
> [[Specifies the number of days a log file will be retained before writing
> over it. You can set the number of days before a log can be overwritten,
> using numbers from 1 to 365. New events will not be added if the maximum log
> size is reached and there are no events older than this period.
> The default setting for this option is 7 days. This is the best choice if
> you want to archive log files weekly.]]
>
> Do not overwrite events (clear log manually)...
> [[Specifies whether existing events will be retained when the log is full.
> If the maximum log size is reached, new events are discarded.
> This option requires that you manually clear the log. Select this option
> only if you must retain all events.]]
>
> The security log on this system is full. Only administrators can log on to
> fix the problem.
>
> "The security log on this system is full" message when you try to
> log on to a computer that is running Windows XP or Windows
> Server 2003
> http://support.microsoft.com/kb/867860
>
> How To Prevent Auditable Activities When Security Log Is Full
> http://support.microsoft.com/kb/140058
>
> STOP 0xC0000244 when security log full
> http://support.microsoft.com/kb/232564
>
> Users cannot access Web sites when the security event log is full
> http://support.microsoft.com/kb/832981
>
> RPC "Server is Unavailable" Message When Audit Log is Full
> http://support.microsoft.com/kb/242361
>
> The event log stops logging events before reaching the maximum log size
> http://support.microsoft.com/kb/312571
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:69216102-6674-4E90-9F31-702F313AE97E@microsoft.com,
> Surfingnewport <Surfingnewport@discussions.microsoft.com> hunted and pecked:
> > Anyone know why the security login keeps filling up in XP Pro. I clear it
> > and it keeps filling up (2 Days or so) for the user with limited rights.
>
>

> Any idea whats going on?

You're the one that's able to read the log.

Group Policy (gpedit.msc) | Local Computer Policy\Computer Configuration\
Security Settings\Local Policies\Audit Policy\
No auditing on all or whatever.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:90F4E7FA-53D1-4568-BD95-150849F9B76D@microsoft.com,
Surfingnewport <Surfingnewport@discussions.microsoft.com> hunted and pecked:
> I clear the security log which I have 512K of space available for it and
> an overwrite when needed selected. Two days later its full again. Any
> idea whats going on?
>
> "Wesley Vogel" wrote:
>
>> Check the Event Viewer Log Size & Overwrite options.
>>
>> Open the Event Viewer...
>> Start | Run | Type: eventvwr | Click OK |
>> Right click Application on the left | Click Properties |
>> On the general tab set Maximum log size to ?? KB |
>> Select Overwrite events older than XX days and set it to ??
>>
>> Right click on the left | Click Properties |
>> On the general tab set Maximum log size to ?? KB |
>> Select Overwrite events older than XX days and set it to ??
>>
>> Right click System on the left | Click Properties |
>> On the general tab set Maximum log size to ?? KB |
>> Select Overwrite events older than XX days and set it to ??
>>
>> Maximum log size...
>> [[Provides a space for you to enter the maximum log file size. Or click
>> the arrows to change the log file size. The default maximum size is 512K.
>> The overwrite options on this tab specify what happens when this limit is
>> reached.]]
>>
>> Overwrite events as needed...
>> [[Specifies whether all new events will be written to the log, even when
>> the log is full. When the log is full, each new event replaces the oldest
>> event.]]
>>
>> Overwrite events older than XX days...
>> [[Specifies the number of days a log file will be retained before writing
>> over it. You can set the number of days before a log can be overwritten,
>> using numbers from 1 to 365. New events will not be added if the maximum
>> log size is reached and there are no events older than this period.
>> The default setting for this option is 7 days. This is the best choice if
>> you want to archive log files weekly.]]
>>
>> Do not overwrite events (clear log manually)...
>> [[Specifies whether existing events will be retained when the log is
>> full. If the maximum log size is reached, new events are discarded.
>> This option requires that you manually clear the log. Select this option
>> only if you must retain all events.]]
>>
>> The security log on this system is full. Only administrators can log on
>> to fix the problem.
>>
>> "The security log on this system is full" message when you try to
>> log on to a computer that is running Windows XP or Windows
>> Server 2003
>> http://support.microsoft.com/kb/867860
>>
>> How To Prevent Auditable Activities When Security Log Is Full
>> http://support.microsoft.com/kb/140058
>>
>> STOP 0xC0000244 when security log full
>> http://support.microsoft.com/kb/232564
>>
>> Users cannot access Web sites when the security event log is full
>> http://support.microsoft.com/kb/832981
>>
>> RPC "Server is Unavailable" Message When Audit Log is Full
>> http://support.microsoft.com/kb/242361
>>
>> The event log stops logging events before reaching the maximum log size
>> http://support.microsoft.com/kb/312571
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:69216102-6674-4E90-9F31-702F313AE97E@microsoft.com,
>> Surfingnewport <Surfingnewport@discussions.microsoft.com> hunted and
>> pecked:
>>> Anyone know why the security login keeps filling up in XP Pro. I clear
>>> it and it keeps filling up (2 Days or so) for the user with limited
>>> rights.