Unable to log a user on "Security Log full"

[wingnuts]

Hello,

I am running Win XP Pro at home and have set up a "Limited"user account for my daughter. All was working fine until recently when she was unable to log on due to the security log file. The message read

"Logon Message"

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

Well that administrator is me, and I can't fix the problem.

I have Norton Anti-Virus which is up to date, SP2 and have changed the log size to maximum, all to no avail.

BTW SP2 and all other software was installed prior to problems.

Any ideas ?


Thanks in advance



Wingnuts

[mazdarx7-64]

login uster the admin account and clear the security log. You will need to set the log so that it will over write as needed in order to stop the problem

[wingnuts]

Thanks for the quick reply.

I have looked everywhere to enable this, but this option is nowhere that I can see.

However, under help it says that it will do this automatically and re-name the file pfirewall.log.old or something like that.

Any further ideas.


Thanks so far


Wingnuts

[Xpirex]

Setting options for logging events

Application and system logging start automatically when you start the computer. Logging stops when an event log becomes full and cannot overwrite itself, either because it has been set for manual clearing or because the first event in the log is not old enough. You use Group Policy to set up security logging.

To define logging parameters for each kind of log, in the Event View console tree, right-click the type of log, and then click Properties. On the General tab, you can set the maximum size of the log and specify whether the events are overwritten or stored for a certain period of time.

The default logging policy is to overwrite logs as needed, provided events are at least seven days old. You can customize this policy for different logs.

The Event log wrapping options include the following.
Use To

Overwrite events as needed:
Have new events continue to be written when the log is full. Each new event replaces the oldest event in the log. This option is a good choice for low-maintenance systems.

Overwrite events older than [x] days :
Retain the log for the number of days you specify before overwriting events. The default is seven days. This option is the best choice if you want to archive log files weekly. This strategy minimizes the chance of losing important log entries and at the same time keeps log sizes reasonable.

Do not overwrite events:
Clear the log manually rather than automatically. Select this option only if you cannot afford to miss an event (for example, for the security log at a site where security is extremely important).

Note • When a log is full and no more events can be logged, you can free the log by clearing it. Reducing the amount of time you keep an event also frees the log if it allows the next record to be overwritten.

• Each log file has an initial maximum size of 512 KB. You can increase the maximum log size to the capacity of the disk and memory, or you can decrease the maximum log size. Before decreasing a log's size, you must clear the log.

I just had the same problem..

[Gait_Keeper]

That's some great info there, really great info

thanx

[wingnuts]

Thanks for the info Xpirex, that's sorted my problem, and thanks again, it's refreshing when someone takes time out to help someone they don't even know.

Thanks


Wingnuts

[Xpirex]

Hey you are more than welcome..

...there is great satisfaction in helping people to resolve problems on their computers.. That's why I joined this place..

Have a great day..

[johnalex44]

You are really very intelligent.