Reporting Errors to Your Primary Support Provider

If you are unable to resolve a problem, contact your primary support provider for assistance. Anytime you receive a server internal error (for example, assertion or access violation (AV)), contact your primary support provider. If you experience an operating system or I/O error, it is most likely a hardware problem. Correct the hardware problem and restore your database. When reporting an error to your primary support provider, be sure to provide the blackbox.trc, SQLDIAG.trc, and SQLDIAG.txt files.

For more information about resolving a 9002 or 1105 space-related error, see Troubleshooting Recovery, Error 9002, and Error 1105.

The xp_trace_setqueryhistory system stored procedure starts a trace consisting of the last 100 queries, including any server exceptions. Trace data is appended to the file named blackbox.trc either when a server exception occurs or when SQLDIAG (located in \Mssql7\Binn) is executed. When SQLDIAG is executed, the last 100 queries, including any server exceptions, are written to SQLDIAG.trc.

SQLDIAG also collects information about server version and configuration, .dll file version, error logs, extended stored procedures, operating system, computer version, configuration data, and other additional data, all of which is put into SQLDIAG.txt.

For example, the environment in which the error occurred includes this information:

• Microsoft® SQL Server™ version number (as reported to the error log or returned by SELECT @@VERSION). The first message written to the error log provides the SQL Server version number.
• DB-Library API version number (as reported by the SQL Server Client Network Utility), ODBC driver version (as reported by ODBC Driver Setup), or OLE DB provider information.
• Application version number (for example, SQL Server Enterprise Manager or osql.exe).
• Operating-system version number.
• Hardware platform.
• Production or development environment.
• This information is also helpful in troubleshooting a problem:
• The message number, message state, and complete error message text.
• Any variables (numbers, database object types, or database object names) included in the error message.
• The context in which the message was generated (what statement was running at the time).
• The number of users who were logged in to SQL Server when the error occurred.
• The frequency with which the error occurs.
• If you are using SQL Server Query Analyzer and you are not seeing more than 255 characters in the results pane, click Query, then click Current Connection Options. Click the Advanced tab, then increase the Maximum Characters Per Column value.

In addition, review error logs and, if running Microsoft Windows NT®, review the Windows NT application log and the sqlstp.log file, located in your \Windows directory. You may also want to use SQL Server Profiler to monitor events.

To help resolve your problem quickly, you may be asked to send your SQLDIAG.txt and error log in e-mail to your primary support provider.

When providing this information, provide the entire error log, including all messages displayed from startup to before or after the error occurred. Be sure to send all information beginning with the time of startup and ending with the error message in question.

Although most startup messages are identical each time you start SQL Server, additional messages sometimes appear during startup, which can provide clues for solving problems that occur during or after startup. If additional messages appear during startup, write down these error messages to assist your support provider in diagnosing and resolving the problem.

See Also