BUG: SQL Exec Fills Event Log w/ Errors After Dr. Watson Entry |
Q140904
The information in this article applies to:
- Microsoft SQL Server version 6.0
BUG# NT: 12396 (6.00)
SYMPTOMS
If Dr. Watson writes an entry into the Windows NT event log after a program has encountered an unhandled exception, SQL Executive can encounter problems reading the Windows NT Application event log. Under these conditions, SQL Executive will write an event log entry approximately every second until the event logfills up (if no wrapping) or is cleared:
Event ID: 318 Category: Alert Engine
Unable to read local EventLog. Reason: The data area passed to a system call is too small.
WORKAROUND
If you clear the event log or shut down SQL Executive, it will stop the event log entries. Changing the default debugger to another program such as NTSD.EXE can prevent this problem from occurring. The DRWTSN32.HLP file has more information on changing the default debugger.
Disabling the "Dump Symbol Table" option from Dr. Watson for Windows NT dialog box (DRWTSN32.EXE) may prevent the problem from occurring.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATION
This problem may be dependent on the amount of information that Dr. Watson writes into the event log. Therefore, it is possible that other application event log entries would cause this behavior. However, the only reported cases of this problem have involved instances where Dr. Watson wrote an entry into the event log.
Any further information about the Dr. Watson program can be found in the DRWTSN32.HLP file installed with Windows NT by default in the %SystemRoot%\system32 directory.
Additional query words: sql6 winnt event log logging error
Keywords : kbinterop kbtool
Issue type :
Technology : kbSQLServSearch kbAudDeveloper kbSQLServ600
Last Reviewed: March 25, 1999 |
