Error log question

[Joe McArthur]

When an application, or in this particular case - my mouse driver software,
encounters some kind of error, and a message appears saying that an error
log is being created, where exactly can I find this error log?

The first thing I did was to search for *.log files on my C: drive. The
files "C:\WINNT\system32\config\software.LOG" and "C:\Documents and
Settings\joemac\NTUSER.DAT.LOG" were among the results, and about the right
timestamp (i.e. coinciding with the error event). Unfortunately I cannot
open either of them, as they are apparently protected by the system from
any outside access.

I then brought up the Event Viewer, under Administrative Tools, and
examined the various logs (Application, Security, and System) but didn't
see anything that looked like it related to my mouse driver error.

So am I not looking in the right place, or just not recognizing the error
in the Event Viewer?

Joe

 

[Pegasus \(MVP\)]

Please quote the exact wording of the screen message you see.

 

[Joe McArthur]

When an application, or in this particular case - my mouse driver
software, encounters some kind of error, ...

To be precise, *it* generated the error(s). Exact dialog wording is:

+----------------------------------------------------------------
|EM_EXEC.exe has generated errors and will be closed by Windows.
|You will need to restart the program.
|
|An error log is being created.
+----------------------------------------------------------------

[snip]

So am I not looking in the right place, or ...

Ahem. I should have said the "wrong" place. If I had looked in the
"right" place then I wouldn't have had to ask the question, right.

Joe

 

[Pegasus \(MVP\)]

Open up c:\winnt and sort your listing by date. The error log is most
likely in there, somewhere near the bottom of the list.

When an application, or in this particular case - my mouse driver
software, encounters some kind of error, ...

To be precise, *it* generated the error(s). Exact dialog wording is:

+----------------------------------------------------------------
|EM_EXEC.exe has generated errors and will be closed by Windows.
|You will need to restart the program.
|
|An error log is being created.
+----------------------------------------------------------------

[snip]

So am I not looking in the right place, or ...

Ahem. I should have said the "wrong" place. If I had looked in the
"right" place then I wouldn't have had to ask the question, right.

Joe

 

[Joe McArthur]

Open up c:\winnt and sort your listing by date. The error log is most
likely in there, somewhere near the bottom of the list.

I'm not seeing it. Should I be looking for a specific name? Of the
files in my C:\winnt directory, which are dated today, 7 out of 17 are
from Windows updates I did today (e.g. "KB828749.log" and
"WindowsUpdate.log"); the remaining 10 are:

setupapi.log
schedLgU.txt
ocgen.log
ockodak.log
comsetup.log
iis5.log
imsins.log
ModemLog_Xircom MPCI+ Modem 56 WinGlobal.txt
imsins.BAK
ShellIconCache

A search through these files for the string "EM_EXEC" turned up nada.

Joe

 

[Pegasus \(MVP\)]

I'm not seeing it. Should I be looking for a specific name? Of the
files in my C:\winnt directory, which are dated today, 7 out of 17 are
from Windows updates I did today (e.g. "KB828749.log" and
"WindowsUpdate.log"); the remaining 10 are:

setupapi.log
schedLgU.txt
ocgen.log
ockodak.log
comsetup.log
iis5.log
imsins.log
ModemLog_Xircom MPCI+ Modem 56 WinGlobal.txt
imsins.BAK
ShellIconCache

A search through these files for the string "EM_EXEC" turned up nada.

Joe

Maybe the author of the faulty program did the right thing and sent
his error log to the event viewer. Run eventvwr.exe and examine
all three logs!

 

[Joe McArthur]

Maybe the author of the faulty program did the right thing and sent
his error log to the event viewer. Run eventvwr.exe and examine
all three logs!

As I said in my original post, I examined the event viewer log files and
saw nothing that appears to me to be related to the mouse driver error. I
just looked again and still see nothing.

The System Log has "error" events listed for the following Sources:

Service Control Manager - Process Tree Service service failed to start.

RemoteAccess - The Remote Access Server could not reset lana 0.

The Application Log has no "error" events listed for today. However, there
is one from yesterday that has an interesting tidbit (notice the very last
sentence):

rasctrs - The description for Event ID ( 2001 ) in Source ( rasctrs )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages
from a remote computer. The following information is part of
the event: The event log file is corrupt..

Does this mean there is a problem with my Event Viewer's log files? If so,
what to do? Thanks.

Joe

 

[Pegasus \(MVP\)]

As I said in my original post, I examined the event viewer log files and
saw nothing that appears to me to be related to the mouse driver error. I
just looked again and still see nothing.

The System Log has "error" events listed for the following Sources:

Service Control Manager - Process Tree Service service failed to start.

RemoteAccess - The Remote Access Server could not reset lana 0.

The Application Log has no "error" events listed for today. However, there
is one from yesterday that has an interesting tidbit (notice the very last
sentence):

rasctrs - The description for Event ID ( 2001 ) in Source ( rasctrs )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages
from a remote computer. The following information is part of
the event: The event log file is corrupt..

Does this mean there is a problem with my Event Viewer's log files? If so,
what to do? Thanks.

Joe

No, it means that the author of the program did not follow sound
programming practices. You will now have to hunt for the file, by
using Start / Search and specifying the date when you believe the
file was created. The file could be anywhere on your hard disk.
Good luck!

An easier way might be to get a different mouse driver.

 

[Joe McArthur]

No, it means that the author of the program did not follow sound
programming practices. You will now have to hunt for the file, by
using Start / Search and specifying the date when you believe the
file was created. The file could be anywhere on your hard disk.
Good luck!

Probably not worth the effort at this point. You'd think the programmers
at Logitech would be a little better than that.

An easier way might be to get a different mouse driver.

I'm going to see if there's a newer one on the Logitech site. Thanks for
the help 'O winged one.

Joe

 

[Joe McArthur]

I'm going to see if there's a newer one on the Logitech site. Thanks
for the help 'O winged one.

Well the newer driver seems to have fixed the problem. Now if MS can only
fix the bug they just introduced into IE, with their latest critical/security
update, whereby mouse clicks on the scroll bar result in a double page
up/down. Uhg!

Joe