Re: 2003 system event log corrupt
- From: Zeezuiper <Zeezuiper@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 8 Jun 2005 02:05:06 -0700
When I read http://support.microsoft.com/?id=258750 it tells me:
"Microsoft recommends that you set all the devices on that path of 10 MB/Sec
and Half Duplex."
Maybe add this little piece of practical information to this article?
By the way, it worked for me, changing the heartbeat NIC to full duplex.
Weird stuff...
"Dave Patrick" schreef:
> I just found out that a network interface running half duplex can cause
> this. The temp fix is to set it up as full duplex.
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Chris" wrote:
> | Hi Dave
> |
> | It pops up a message saying "The event log file is corrupt" when I try to
> | view the system log. When I ok this it leaves a red x on the system part
> of
> | event viewer along with "there are no items to show in this view." The
> | serurity & application logs are ok.
> |
> | Chris.
>
>
>
.
- Follow-Ups:
- Re: 2003 system event log corrupt
- From: geirhald
- Re: 2003 system event log corrupt
- From: Dave Patrick
- Re: 2003 system event log corrupt
- References:
- Re: 2003 system event log corrupt
- From: Dave Patrick
- Re: 2003 system event log corrupt
- Prev by Date: Re: Services Won't Start
- Next by Date: file permission for append-only
- Previous by thread: Re: 2003 system event log corrupt
- Next by thread: Re: 2003 system event log corrupt
- Index(es):
Relevant Pages
|
