Hey MS...3 new Blank Event Viewer threads since yesterday...

  • Thread starter Thread starter Charles Otstot
  • Start date Start date
C

Charles Otstot

Is there any chance that those of you from MS can even acknowledge that
there is an issue with Win2K SP4 Event Logs?
While many here understand it takes time to diagnose and develop a fix for a
problem such as this, it is difficult to understand how so many instances
(I've counted 20+ threads since early September) of an identical problem can
go completely unanswered by your organization.
It seems reasonable (at least to me) that the organization could at least
acknowledege the problem exists and give some information on whether you
will attempt to create a permanent fix.
Please folks, let us know *something*!

Charlie O.
 
Hi Charles,

The problem you have, I have had also. What I did was to rebuild the Event log
files.To do this, I first went to Services and disabled Event log. After booting
I searched for *.evt. The three file are appevent.evt, secevent.evt, and
sysevent.evt. They are located in ..\config\<file>
I deleted each one of those and rebooted. Haven't had any other problems out of
them at all. I do pay more attention to the events now, and actually have more
respect for taking care of the problems and learn a great deal about where the
problems come from. Some that looked like monumental problems are actually small
and are generally caused by me. And example is DHCP squawking and the cause was
that I had timed programs to start, like email (send&receive), and had the modem
disabled while away. Oh, and after knowing more, I clear the squawks out to a
clean slate more often. Probably lemonade I would say.

I hope this helps, and maybe you can help a few out, since you know how it feels
to be in need.

And a tip, if I may, I use my spell checker to file files that I need in the
body of some posts like mine that written out in prose as opposed to good
outline form. Not much of a tip; well, I didn't think it was much of an answer
either, but if it worked for yas, it did the job. Good luck.



good computing,
--
:o)
don
---------
P.S. These guys and girls work their hearts out here for self satisfaction and
little bit of praise.
---------


Is there any chance that those of you from MS can even acknowledge that
there is an issue with Win2K SP4 Event Logs?
While many here understand it takes time to diagnose and develop a fix for a
problem such as this, it is difficult to understand how so many instances
(I've counted 20+ threads since early September) of an identical problem can
go completely unanswered by your organization.
It seems reasonable (at least to me) that the organization could at least
acknowledege the problem exists and give some information on whether you
will attempt to create a permanent fix.
Please folks, let us know *something*!

Charlie O.
 
Sorry Charles,

I didn't realize you were already aware of this. I try to go down through all
the new posts, but I have had to work hard this week. Most of the folks know
that I trade for a living, and really felt good today. Up nearly $600k for the
week. Anyway, I'm sure you didn't want to hear that. Anyway, hope you help
others .

--
:o)
don
---------



Hi Charles,

The problem you have, I have had also. What I did was to rebuild the Event log
files.To do this, I first went to Services and disabled Event log. After booting
I searched for *.evt. The three file are appevent.evt, secevent.evt, and
sysevent.evt. They are located in ..\config\<file>
I deleted each one of those and rebooted. Haven't had any other problems out of
them at all. I do pay more attention to the events now, and actually have more
respect for taking care of the problems and learn a great deal about where the
problems come from. Some that looked like monumental problems are actually small
and are generally caused by me. And example is DHCP squawking and the cause was
that I had timed programs to start, like email (send&receive), and had the modem
disabled while away. Oh, and after knowing more, I clear the squawks out to a
clean slate more often. Probably lemonade I would say.

I hope this helps, and maybe you can help a few out, since you know how it feels
to be in need.

And a tip, if I may, I use my spell checker to file files that I need in the
body of some posts like mine that written out in prose as opposed to good
outline form. Not much of a tip; well, I didn't think it was much of an answer
either, but if it worked for yas, it did the job. Good luck.



good computing,
--
:o)
don
---------
P.S. These guys and girls work their hearts out here for self satisfaction and
little bit of praise.
---------


Is there any chance that those of you from MS can even acknowledge that
there is an issue with Win2K SP4 Event Logs?
While many here understand it takes time to diagnose and develop a fix for a
problem such as this, it is difficult to understand how so many instances
(I've counted 20+ threads since early September) of an identical problem can
go completely unanswered by your organization.
It seems reasonable (at least to me) that the organization could at least
acknowledege the problem exists and give some information on whether you
will attempt to create a permanent fix.
Please folks, let us know *something*!

Charlie O.
 
Hey Don,

Yep..I'm just trying to make a post that might be visible enough for one of
the MS guys to respond. Since the postings have shown pretty clearly that
the issue is widespread and limited to Win2K SP4 systems, it seems
reasonable that MS should have this as an open isue under investigation.
Like you, we havent had any issues with affected servers once we recreated
the logs, but obviously, we cannot guarantee that the "fix" is indeed
permanent. Even if recreation is the final answer (i.e no hotfix comes out),
knowing the underlying cause is just as important as knowing the corrective
measures.
Good luck with your trading in the next two days!

Charlie
 
Hello Charles,

There is a hotfix for this issue...
829246 Event Logs Are Corrupted
http://support.microsoft.com/?id=829246

--
Robert Mitchell
Windows NT4&2000 MCSE
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Robert Mitchell said:
Hello Charles,

There is a hotfix for this issue...
829246 Event Logs Are Corrupted
http://support.microsoft.com/?id=829246

--
Robert Mitchell
Windows NT4&2000 MCSE
Microsoft Enterprise Support

This posting is provided "AS IS" with no warranties, and confers no rights.


<Snip>
Click to expand...


Thank you Robert!!

I'll make sure to keep this and will pass it on when I see new threads pop
up on the issue.

Charlie
 
Back
Top