Dr. Watson Error messages

TYPE "DRWTSN32" IN THE RUN BOX (START|RUN). YOU WILL OPEN THE DR WATSON LOG APPLET. IT MAY ALREADY POINT TO THE PATH FOR DR WATSON LOGS IF IT DOES THEN YOU WILL SEE A LIST IN THE WHITE SPACE TITLED "APLICATION ERRORS" YOU WILL HAVE AS MANY ERRORS LISTED AS YOU HAVE INCURRED HIGHLIGHT THE MOST RECENT ONE AND SELECT "VIEW" THIS MAY HELP TO YOU IN DEFINING THE PROBLEM. THEN AGAIN MAYBE NOT SINCE MOST OF THE DATA IS VERY TECHNICAL. THE FIRST PAGE WILL GIVE SOMETHING TO WORK WITH. The following is a description of the procedure used to locate the cause of an actual DNS crash. The relevant excerpts from the Dr. Watson logs are included below, to show how this process was completed. The red text in brackets following some of the numbered steps are the answers found in the logs supplied below.

1.Find the process id (pid) that actually crashed ( pid=148)

2.Search forward to find the service associated with that pid (148 dnssvc.exe)

3.Search forward from there for the string ‘fault’ (FAULT ->78003664 8a11)

4.Search backwards from there to find the thread number that caused the fault (Thread Id 0x161)

5.Convert that thread number from hexadecimal to decimal using Windows calculator (hexidecimal 0x161 = decimal 353)

6.Search the DNS logs for that thread number (<353) and this will tell you what the service was doing when it crashed. In our example, the DNS logs showed that thread number 353 was responding to a query for a particular hostname resolution (the name has been removed from the example).

[<353> ReadQuestion(116450429): N=, C=IN (1), T=ANY (255)]

THIS HAS TO DO WITH A DNS ERROR BUT THE PRECEDURE SHOULD GUIDE YOU. TO PRINT THE LOG RIGHT CLICK IN THE LOG PAGE , SELECT ALL AND COPY THEN PASTE IN WORD PROCESSOR.

This question was closed by the author

This question was closed by the author