Troubleshooting using event Viewer
beginner
search for the first / earliest warning or error event to see the real cause
of problem.
Question:
1. Does the first / earliest warning/error events always provide the source
of problem ?
2. Is that possible that a dependent service runs faster than the master
service & create an error ? If so, what is the best way to find the
valiable information among the logs ?
Thanks.
David Sengupta [MVP]
--
David Sengupta M.T.S., B.Sc., MCSE, Exchange MVP, CCA
Ottawa, Canada
My Latest Whitepaper: e-Discovery for Exchange Environments
http://wm.quest.com/msnewstb
"beginner" <begi...@abc.com> wrote in message
news:e4JKaCFV...@TK2MSFTNGP15.phx.gbl...
> In general, in case of system problem, I will check the event viewer &
> search for the first / earliest warning or error event to see the real
> cause of problem.
>
> Question:
> 1. Does the first / earliest warning/error events always provide the
> source
no. sometimes you need to correlate events across system & application logs
to reconstruct the earliest event. Sometimes the eariest warnings/errors
are unrelated to the root cause of whatever issue you're troubleshooting ...
i.e. there could be numerous concurrent issues happening where event
sequences are inter-leaved. And sometimes there just isn't an easy way to
make sense of issues through reading the logs.
> of problem ?
> 2. Is that possible that a dependent service runs faster than the master
> service & create an error ? If so, what is the best way to find the
> valiable information among the logs ?
> Thanks.
>
are you asking if there is a problem if a dependent service starts prior to
it's 'parent'? There can be, yes ... though I think that in most/all cases
the dependent service just won't start (because it can't). You'd want to
look for the service name or similar as source in the event logs ... system
or application.
hope that helps some
>
>