WINS logs fill up C drive

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a Win2k DC that is a WINS, DNS, File and Print server (it was upgraded
from a NT 4 PDC by a previous admin). The problem is that in a period of
about two hours, WINS will generate over 1300 1 MB .log files in the
C:\Winnt\System32\WINS directory and it fills up the c drive (which only has
1.4 GB free since it is limited to a 4 GB partition from the upgrade). Once
the drive fills up, the printers stop working. I can go in and manually
delete the .log files and restart the print spooler service and everything is
fine.

This has happened twice in the past three weeks and it all happens in a two
hour period (between 6:00 am - 8:00 am). I haven't noticed until someone
complains of printing problems.

The only error in event viewer is WINS 4224 that says a serious error has
occured and I should check the application log for a ESENT error. The only
ESENT error in the application log says that WINS can not be updated due to
low disk space on the log disk.

I hope this makes sense and any help would be appreciated. Thanks in advance!
Shawn
 
Did you figure out what this was? I am having the same proble
suddenly.

*I have a Win2k DC that is a WINS, DNS, File and Print server (it wa
upgraded
from a NT 4 PDC by a previous admin). The problem is that in
period of
about two hours, WINS will generate over 1300 1 MB .log files in the
C:\Winnt\System32\WINS directory and it fills up the c drive (whic
only has
1.4 GB free since it is limited to a 4 GB partition from th
upgrade). Once
the drive fills up, the printers stop working. I can go in an
manually
delete the .log files and restart the print spooler service an
everything is
fine.

This has happened twice in the past three weeks and it all happens i
a two
hour period (between 6:00 am - 8:00 am). I haven't noticed unti
someone
complains of printing problems.

The only error in event viewer is WINS 4224 that says a serious erro
has
occured and I should check the application log for a ESENT error.
The only
ESENT error in the application log says that WINS can not be update
due to
low disk space on the log disk.

I hope this makes sense and any help would be appreciated. Thanks i
advance!
Shawn
Click to expand...


-
acaputo31
 
Did you find a solution for this yet? I just started having the same log
phenomenon...although I get no errors anywhere.
 
Go into GPO and modify your logs so that they are only so big, and are
overwritten within one day. If it's within a given time frame I would
look for what is running at that time and what the log files are
telling you, then correct the original problem. Without the log files
to look at I can't really tell you much more.

Randy
 
Acaputo - No, I still haven't figured it out. Is your DC also an upgrade
from NT 4.0?

RandyC - Thanks for the post, but it isn't the log file in event viewer that
is filling up. WINS is generating numberous 1.0 MB *.log files and dumping
them into the C:\Winnt\System32\WINS directory which ultimately fills up the
c: drive.

The only errors offered by event viewer are that the c: drive is
full...which is caused by the WINS "problem". I say "problem" b/c I haven't
noticed any resolution issues.

Thx,
S
 
Anyone find the solution to this...I am also having the same problem with the
win log files filling up my C drive.

Paddy
 
I could also use some help on this one. My C: is also filling up because of
the log files.

Thank you
Shawn Wilson
 
After going through log file and finding the computer name I was able to
disable the DDE on that machine. The log files stop and everything went back
to normal.

"It had a service called NetDDE (Network Dynamic Data Exchange) enabled. We
don't use it here and I am not sure how it got enabled. Once, I disabled
it off the client my problems was resloved."

Shawn Wilson
 
Back
Top