Re: win 2000 log files

From: karl [x y] (jamescagney90210@excite.com)
Date: 08/15/02


From: "karl [x y]" <jamescagney90210@excite.com>
Date: Wed, 14 Aug 2002 20:24:57 -0400


In addition to the other posts, I would add that when a server is
accidentally rebooted, you probably won't have much in the event logs to
differentiate it from a system lockup. Running what used to be called
"Performance Monitor" temporarily might help provide some additional
information [CPU and memory utilization, etc], and I think there was one or
more articles on using Perf Mon to troubleshoot problems at
www.microsoft.com/support. Regarding debugging dumps, I believe that it
requires a savvy programmer and/or Microsoft tech support to turn a dump
into a resolution.

You may want to enable event auditing for failed and some successful events
[like logons and maybe accesses to certain files] to determine who, if
anyone, was logged into a server when it rebooted, and to some extent what
they were doing [and avoid using shared login IDs for server
administrators]. It might be helpful also if you use a program like
IPsentry that monitors the server [as well as ASP errors in the event log,
etc.] and immediately pages you when the server stops responding, so that
you can have someone run up there and see if someone is standing there
looking guilty. Also, if you want to collect information on whether the
power source is fluctuating, you could put a UPS on the server that has the
ability to add power events to the Windows event log. A malfunctioning UPS
and/or power fluctuations can cause spontaneous reboots.

"julien" <julien@nettheory.com> wrote in message
news:27c901c243c7$10a0ed10$39ef2ecf@TKMSFTNGXA08...
> Hi,
>
> I am trying to view the logs on my win 2000 server.
> There are not much information in the event viewer, so I
> am searching a way to find more information when a problem
> occurs when the server crashes.
> I set up Dr Watson, but the information is not always
> really clear. I also installed autodump +.
> I am basically searching for all the log files posscible
> when a server is accidentaly rebooted or when ASP or IIS
> crashed,
>
> Thanks for any help.
>
> Julien



Relevant Pages

  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... error 15100 Win32 Error 15100. ... One is indicating it can't retrieve info about the System log. ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... test network connectivity to local domain controllers. ... Directory Server Diagnosis ... Verifying that the local machine ALPHA, ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... (Event String (event log = Directory Service) ...
    (microsoft.public.windows.server.sbs)
  • Re: Server2003 2008 error !!
    ... Remove the x.x.1.x form the NIC of the DCs and configure it as a FORWARDER or use directly the ISPs DNS server as Forwarders in the DNS server properties in the DNS management console. ... On the 2008 make sure the internal firewall is not blocking AD replication, by default the firewall is enabled ion 2008. ... The event log File Replication Service on server ... EventID: 0x000003EE ...
    (microsoft.public.windows.server.active_directory)
  • Re: What are the best general things to do after a dirty shutdown (Server SBS)
    ... Microsoft Windows Small Business Server 2003 Best Practices Analyzer ... After that, please post any event log errors, just the EventID# and Source names, not the whole error message. ... One is indicating it can't retrieve info about the System log. ...
    (microsoft.public.windows.server.sbs)