Re: System Event Log Corrupt
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 12 Aug 2005 03:53:32 GMT
Hi Dave,
How are you doing? Do you have chance to perform test and found the root
cause?
Thanks for Alex's kindly knowledge sharing! Based on my research, I think
your issue is very similar with the known issue described in the KB
article. Please refer to get detail information:
You receive a "The event log file is corrupt" error on a computer that is
running Windows Server 2003 SP1, an x64-based version of Windows Server
2003, or Windows XP Professional x64 Edition
http://support.microsoft.com/default.aspx?scid=kb;en-us;899416
I suggest you contact Microsoft Product Support Services to obtain the
hotfix. For a complete list of Microsoft Product Support Services telephone
numbers and information about support costs, visit the following Microsoft
Web site:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note: In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The usual support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.
If you have any further question or concern on the issue please feel free
to let me know. I am looking forward to your reply!
Have a nice day!
Best Regards,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: System Event Log Corrupt
>thread-index: AcWe5pQlrnXuuiOsT3u/bRvpaLmvuw==
>X-WBNR-Posting-Host: 131.107.0.102
>From: =?Utf-8?B?QWxleCBTdXR0b24gW01TRlRd?= <asutton@xxxxxxxxxxxxxxxxxxxx>
>References: <#vzj7AdmFHA.3336@xxxxxxxxxxxxxxxxxxxx>
<JSaMkQ$mFHA.3472@xxxxxxxxxxxxxxxxxxxxx>
<uiDVc4$mFHA.2580@xxxxxxxxxxxxxxxxxxxx>
>Subject: Re: System Event Log Corrupt
>Date: Thu, 11 Aug 2005 19:36:01 -0700
>Lines: 209
>Message-ID: <E41735E2-2414-4C65-88D0-563764BAA22F@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:143545
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>This is a known issue with how the network card driver raises events.
Please
>see KB article
http://support.microsoft.com/default.aspx?scid=kb;en-us;899416
>
>There is a hotfix available from Microsoft Product Support. You need to
call
>and reference your symptoms and the KB article above 899416.
>
>
>cheers
>alex
>
>
>--
>This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>"Dave Taylor" wrote:
>
>> Jenny,
>>
>> I have "scrubbed" the server as I a few more days to before I put it on
the
>> customers site. I have already gone through the what you have mentioned
at
>> the end of your post.
>>
>> I have just done a search for the post that I found re the cluster and
>> network card speed. I didn't find that but I did find the following:-
>>
>> <snip>
>> Intel 10/100/1000 GHz V8.4.21.0, the
>> driver is Intel Pro 1000 MT V8.4.21.0
>>
>> Sorry for the delay, I was travelling last week. Those are the cards
that
>> we see the issue on. Are the netcards running in half duplex ( 10 Mb),
if
>> you can move them to
>> full duplex and reboot the machine it may resolve the issue or you can
try a
>> different netcard. We are aware of the issue and working on an update
for
>> it.
>>
>> Thanks,
>> Darrell Gorter[MSFT]
>> <end of snip>
>>
>> Do we have an update as this is the same card that I am using?
>>
>> Thanks
>>
>> Dave
>>
>> ""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:JSaMkQ$mFHA.3472@xxxxxxxxxxxxxxxxxxxxxxxx
>> > Hi Dave,
>> >
>> > Thanks for posting here.
>> >
>> > For your description, I understand that there is an error message
>> > indicating that the system event log file is corrupted. If I am
off-base
>> > on
>> > that, please let me know.
>> >
>> > I am sorry for the delayed response due to weekend. Please understand
that
>> > the newsgroups are staffed weekdays by Microsoft Support professionals
to
>> > answer your systems and applications questions. Your understanding is
>> > greatly appreciated!
>> >
>> > Before we go any further, could you help me some information, so that
we
>> > can offer the exact solution for to solve the issue?
>> >
>> > 1. Please paste me the screen shot of the error message and the related
>> > event error log in detail.
>> >
>> > 2. What is mean when you set the network card to 100Mb Full Duplex and
>> > reboot the server it is OK?
>> > Does the error message disappear? Did you find any errors in event log?
>> >
>> > Corrupted event log may occur if an open handle controls the event log
>> > file, if Symbols for Dr. Watson Error Debugging installed and the more
>> > likely, the file is corrupted. It is hard to restore these event log
files
>> > unless you restore the system by NTBACKUP or SBS BAKUP console if these
>> > logs are critical to you.
>> >
>> > The steps below are used to create new event log files.
>> >
>> > 1. Open Event Viewer.
>> > 2. Right click the System Log, select Clear All Events, you can select
to
>> > save the log before you clear it. (In some cases, we can keep the
event
>> > log
>> > contents by this method)
>> > 3. Repeat step 2 on other log category if they reported that they are
>> > corrupted.
>> > 4. Restart computer and check if the issue is resolved.
>> >
>> > If the issue still exists, do the following:
>> >
>> > 1. Click Start->Run, type "services.msc" (without the quotation marks)
and
>> > then press Enter.
>> >
>> > 2. Double-click "Event Log"
>> >
>> > 3. Choose "Disabled" in the Startup type box.
>> >
>> > 4. Click OK.
>> >
>> > 5. Restart the computer.
>> > NOTE: When the system starts up, several services may fail; a message
>> > informing the user to use Event Viewer to review errors may appear.
>> >
>> > 6. Open My Computer and go to C:\WINDOWS\system32\config
>> >
>> > 7. Locate SysEvent.evt file, right-click it and then click Rename.
>> >
>> > 8. Type "Sysevent.old"(without the quotation marks) and then press
Enter.
>> > NOTE: You may need repeat step 7 and step 8 on all the affected event
log
>> > files.
>> >
>> > 9. Click Start->Run, type "services.msc" (without the quotation marks)
and
>> > then press Enter.
>> >
>> > 10. Double-click "Event Log"
>> >
>> > 11. Choose "Automatic" in the Startup type box.
>> >
>> > 12. Restart the computer and then check if the issue is fixed.
>> >
>> > The following article will be helpful:
>> > 172156 How to Delete Corrupt Event Viewer Log Files
>> > http://support.microsoft.com/?id=172156
>> >
>> > I appreciate you time and effort. I am currently standing by for you
>> > about
>> > the test result. I am always happy to be of further assistance.
>> >
>> > Have a nice day!
>> >
>> > Best Regards,
>> >
>> > Jenny Wu
>> > Microsoft CSS Online Newsgroup Support
>> > Get Secure! - www.microsoft.com/security
>> > ======================================================
>> > This newsgroup only focuses on SBS technical issues. If you have issues
>> > regarding other Microsoft products, you'd better post in the
corresponding
>> > newsgroups so that they can be resolved in an efficient and timely
manner.
>> > You can locate the newsgroup here:
>> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>> >
>> > When opening a new thread via the web interface, we recommend you
check
>> > the
>> > "Notify me of replies" box to receive e-mail notifications when there
are
>> > any updates in your thread. When responding to posts via your
newsreader,
>> > please "Reply to Group" so that others may learn and benefit from your
>> > issue.
>> >
>> > Microsoft engineers can only focus on one issue per thread. Although we
>> > provide other information for your reference, we recommend you post
>> > different incidents in different threads to keep the thread clean. In
>> > doing
>> > so, it will ensure your issues are resolved in a timely manner.
>> >
>> > For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> > check http://support.microsoft.com for regional support phone numbers.
>> >
>> > Any input or comments in this thread are highly appreciated.
>> > ======================================================
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> > --------------------
>> >>From: "Dave Taylor" <noemail@xxxxxxxxx>
>> >>Subject: System Event Log Corrupt
>> >>Date: Fri, 5 Aug 2005 16:13:24 +0100
>> >>Lines: 18
>> >>X-Priority: 3
>> >>X-MSMail-Priority: Normal
>> >>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>> >>X-RFC2646: Format=Flowed; Original
>> >>Message-ID: <#vzj7AdmFHA.3336@xxxxxxxxxxxxxxxxxxxx>
>> >>Newsgroups: microsoft.public.windows.server.sbs
>> >>NNTP-Posting-Host: 62-249-231-10.no-dns-yet.enta.net 62.249.231.10
>> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>> >>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:141862
>> >>X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >>
>> >>All,
>> >>
>> >>I have just done a clean install of SBS2003 with SP1 on a Dell 1800
>> > Server.
>> >>When I go to the System log it says that it is corrupt. I clear it
down
>> > and
>> >>events are logged. Reboot the server but it get corrupt again. I have
>> > done
>> >>this process 4 or 5 times but always the same. After a reboot it is
>> >>corrupt. I have even disabled the event log and cleared all the files,
>> >>restarted and then rebooted but still the same.
>> >>
>> >>I did a Google on this and found a couple of posts about people having
the
>> >>same problem when using clustered servers. If I set the network card
to
>> >>100Mb Full Duplex and reboot the server it is OK. Has anyone else seen
>> > this
>> >>or do I have anything to worry about on the server?
>> >>
>> >>TIA
>> >>Dave
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>
.
- References:
- System Event Log Corrupt
- From: Dave Taylor
- RE: System Event Log Corrupt
- From: "Jenny wu [MSFT]"
- Re: System Event Log Corrupt
- From: Dave Taylor
- Re: System Event Log Corrupt
- From: Alex Sutton [MSFT]
- System Event Log Corrupt
- Prev by Date: Re: Help! I'm new and have many questions!
- Next by Date: RE: Help please
- Previous by thread: Re: System Event Log Corrupt
- Next by thread: RWW vs. VPN
- Index(es):
Relevant Pages
|
