Application Log Full SBS 2000 Server

[Educated Kid]

Help,

I keep getting an Application Log Full message on my
Small Business Server running Windows 2000. No matter
what I do with the logging settings they always default
back to the system default. I want the log to only log
warning and critical events plus overwrite as required.
It allows changes back to loging every event plus stops
when full thus displaying the message "Application Log
Full".

This was an known problem in early versions of Windows NT
although there was a fix brought out for it, according to
the support information. A search on the Microsoft site
only found the old NT problems, nothing on Windows 2000.

Does anyone know how I can fix this very frustrating
problem?

 

[Oli Restorick [MVP]]

Where are you making the changes? In the default domain controllers policy
(in Group Policy), or elsewhere?

Regards

Oli

 

[Guest]

Hi,

From within the application log while viewing the Event
viewer.

 

[Mark Brown[MSFT]]

| From: "Educated Kid" <[email protected]>
| Sender: "Educated Kid" <[email protected]>
| Subject: Application Log Full SBS 2000 Server
| Date: Sun, 25 Jul 2004 01:46:05 -0700
|
| Help,
|
| I keep getting an Application Log Full message on my
| Small Business Server running Windows 2000. No matter
| what I do with the logging settings they always default
| back to the system default. I want the log to only log
| warning and critical events plus overwrite as required.
| It allows changes back to loging every event plus stops
| when full thus displaying the message "Application Log
| Full".
|
| This was an known problem in early versions of Windows NT
| although there was a fix brought out for it, according to
| the support information. A search on the Microsoft site
| only found the old NT problems, nothing on Windows 2000.
|
| Does anyone know how I can fix this very frustrating
| problem?
|
|
|
|
|

Hi Educated,

I have found this article that may apply to your SBS server and this Event
log corruption.
One thing it does not state is that you should always copy or export this
log to a safe place
prior to fixing this issue.

Please refer to article
http://support.microsoft.com/default.aspx?scid=kb;en-us;829246

This should fix your issue.
Thanks

~~ Mark Brown ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Educated Kid]

Many thanks for this update Mark. Will investigate this
further.

Regards,

Educated

-----Original Message-----
| From: "Educated Kid"