Dr Watson dumping - Not logging.

  • Thread starter Thread starter deanotex
  • Start date Start date
D

deanotex

I have configured Dr Watson so it is catching application terminations
and dumping. It is not writing a "DrWatson" event to the Application
log.

Does anyone know what resgistry key controls that?

I have looked under
\HKLM\SYSTEM\ControlSet\Services\EventLog\Application, and
DrWatson is in the Sources key. There is also a subkey called
DrWatson.

I'd like to be able the generate an App Term report using psloglist
enterprise wide, but without this event I'm stuck. Why is this
failing?

Jeff
 
Well maybe Dr Watson is not set up correctly.

1. Do you get the log and memory dump files in the default Dr Watson
location when an app crashes? The default location is %Documents and
Settings%\All Users\Application Data\Microsoft\Dr Watson.
2. Have you included the "Dr. Watson Debugger" component in your build? XPe
SP2 ships with this component. If using XPe SP1, download this component
at:
http://www.microsoft.com/downloads/details.aspx?FamilyID=6497291e-19e5-41a6-
9192-68ec1da281df&DisplayLang=en
3. Was Dr Watson set up as the default post-mortem debugger, i.e. the
debugger that the system calls on an app crash? You can check what the
post-mortem debugger is by checking the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\AeDebug\Debugger. If it's not drwtsn32.exe, you can set
it back to Dr Watson by running the following command in a command window:
drwtsn32.exe -i.

Once Dr Watson is correctly setup, make sure the following registry value
exists, which will be used to interpret Dr Watson event logs
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\Dr
Watson
EventMessageFile = %Windows%\System32\drwtsn32.exe

KS

This posting is provided "AS IS" with no warranties and confers no rights.
 
1) Yes we are getting user.dmp and drwtsn32.log's generated.
2) No, Dr Watson was not include in our initian compenent build. Changes
were made to the registry manually to enable Dr Watson. Those include:

\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\win.ini
\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDubug
\HKLM\SOFTWARE\Microsoft\DrWatson

These changes were added manually to 2500 machines because were operating in
a kiosk environment. Running drwtsn32 -i was not an option as the GUI always
fronts our application.

The entry in:

HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\Application\DrWatson

already existed. Additionally, in the Application key "DrWatson" in in the
sources string. All this should in enable the message.

The QFE referenced updates the SLD's for our configuration. As we've
already rolled this configuration out to 2500 sites and by all outward
appearances have the regitry keys set up correctly, will the installation of
SP2 then enable this Application event logging?
--
Slater...

Jeff

"Time is an illusion, rising from time."
 
How are you intending to install SP2 on the devices in the field?
I mean it is possible but going to be quite big effort.

When you deployed Dr.Watson binaries manually on the devices in field, did you test it first? More specifically, did you run the
binaries through DependencyWalker to see if all the dependencies were in your image and, more important since you're using latest
Watson component binaries on old image, did you see any entrypoint conflicts there?

=========
Regards,
KM
 
Back
Top