Diagnosing General ODBC Errors

This topic discusses how to diagnose issues that may arise when using the Microsoft® SQL Server™ ODBC Driver.

• The szErrorMsg string returned by SQLDiagRec() starts with:

  "[Microsoft][ODBC SQL Server driver][DBMSxxxx]"

    

  If DBMSxxxx is the name of a SQL Server Client Net-Library, the problem is a connectivity or network problem. For more information, see Diagnosing ODBC Connection Errors.

• The szErrorMsg string returned by SQLDiagRec() starts with:

  "[Microsoft][ODBC SQL Server driver][SQL Server]"

    

  The error is coming from SQL Server. The pfNative variable returned by SQLError() is the SQL Server error code. Follow the directions for this error number in ODBC Error Message Format. Also, you should review the problem with the database administrator.

• If you are experiencing difficulties with stored procedures that reference temporary tables on SQL Server 6.0 or later, make sure that the CREATE TABLE statements for the temporary tables specify NULL or NOT NULL for each column. For more information, see CREATE PROCEDURE.
• If you are experiencing differences in behavior between DB-Library and ODBC clients, or in ODBC clients upgraded from earlier versions of SQL Server, these could be due to different options set by the SQL Server ODBC driver. For more information, see Effects of SQL-92 Options.
• If you are experiencing Microsoft Access conformance errors, or if calls to the ODBC catalog API functions are failing, ensure the right version of Instcat.sql was run in the target server. For more information, see Upgrading the Catalog Stored Procedures (ODBC).
• If you are experiencing syntax errors from either SQL Server:

  szSqlState = "37000", *pfNativeError = 170,

  szErrorMsg="[Microsoft][ODBC SQL Server Driver][SQL Server]

                 Line 1: Incorrect syntax near '*'."

    

  or from the ODBC SQL Server Driver, you need to determine if the problem is with the SQL statements given to the SQL Server ODBC driver by the application, or with the Transact-SQL statements generated by the driver.

  Use the ODBC trace to see the SQL statements passed from the application to the SQL Server ODBC driver. The ODBC trace is activated from the ODBC icon in Control Panel.

  If the trace shows that the SQL statements coming from the application are not using valid Transact-SQL or ODBC SQL syntax, diagnose the application.

  If the trace shows that the application is passing valid Transact-SQL or ODBC SQL statements to the driver, use SQL Server Profiler to trace the Transact-SQL statements sent from the SQL Server ODBC driver to SQL Server. For more information, see Monitoring with SQL Server Profiler.