Re: Event log/viewer
- From: "KM" <konstmor@xxxxxxxxxxxxxxxx>
- Date: Mon, 4 Apr 2005 14:19:30 -0700
Larry,
You basically answered your questions yourself.
The "Event Log" component you added is to support the logging but not to view the logs. (just the EventLog service)
You will need the "Administration Support Tools" and all its dependencies to add the Event Viewer properly. If you don't want to add
all bunch of components you will have to analyze the dependencies and resolve only those that are really needed to support the Event
Viewer (may appear to be a laborious work just to get the Event Viewer working).
Personally I prefer copying the Event Log files (*.evt) offline to XP Pro machine and review them there with Event Viewer.
The paths to log files you will find under [HKLM\System\CurrentControlSet\Services\EventLog\Application] key and by default they are
set to %SystemRoot%\system32\config\*.Evt (e.g, AppEvent.Evt, SysEvent.Evt, SecEvent.Evt, etc.). (just following the instructions
from here : http://support.microsoft.com/default.aspx?scid=kb;en-us;315417&sd=tech)
Another alternative would be using a 3rd party Event log viewing software that does not depend on so many things as Microsoft on
does. I'd think that Resource Kit probably has such simple tool but I never searched there for it. You may want to search for
dumpel.exe.
Also, in the Server Kit there are some command line tools to query, create and trigger events in the logs. I don't think this is a
good solution for you as it would required heavy script engines at least but you may still want to take a look at it:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/68672494-7700-4cbf-8392-4b6ef87b8749.mspx
Connecting to Event Viewer log from another computer is another story. I think this going to work only if you include the entire
Administration Support Tools but I am not positive.
--
Regards,
KM, BSquare Corp.
> I want to just add Event log support to my target system. I added the Event
> Log component but wasn't able to view the log locally and couldn't connect
> remotely to view it. I tried copying the eventvwr.exe but that needed the
> eventvwr.msc but that needed MSC support. I filtered the components and the
> only one I found eventvwr.exe in is the Administration Support Tools. But
> added that blows my image size up from 62MB to 160MB! Isn't there a
> component for just Event Log support? If not, any ideas what minimal things
> I need to support MSC so that I can run the viewer? And am I correct that
> the reason I can't remotely connect to view the log is because there's no
> viewer support on the target or could there be some other reason? If I can
> connect remotely without it, I don't really need the local viewer support.
.
- Follow-Ups:
- Re: Event log/viewer
- From: Larry Waibel
- Re: Event log/viewer
- References:
- Event log/viewer
- From: Larry Waibel
- Event log/viewer
- Prev by Date: Event log/viewer
- Next by Date: Re: What is requiered for a valid DHCP client?
- Previous by thread: Event log/viewer
- Next by thread: Re: Event log/viewer
- Index(es):
Relevant Pages
|
