BUG: ODBC TDS Error Calling Procedure with SQLTrace.

Last reviewed: April 9, 1997
Article ID: Q154891

The information in this article applies to:

Microsoft SQL Server, version 6.5

SYMPTOMS

If you call a procedure with the ODBC driver while providing a NULL parm, such as the following example:

   SQLExecDirect(hstmt, "{call TstPrc('Val1',NULL,'Val3')}", SQL_NTS);

and SQL Trace is active, the following error message appears:

   SQLState: S1000, pfNative: 9
   ErrorMsg: [Microsoft][ODBC SQL Server Driver]
             Protocol error in TDS stream

WORKAROUND

Use the 4032 trace flag to trace the calls from the driver. For more information, please see the Trace Flags section in the Transact-SQL Reference guide.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft SQL Server ODBC Driver version 2.65.0201. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: 2.65.0201 2.65.0212 trace
Keywords : kbnetwork SSrvGen SSrvTran_SQL
Version : 2.65.0201 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.