FIX: Spid Missing with Trace Flag 4032 on RPC Events

Last reviewed: June 27, 1997
Article ID: Q165389

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 16566 (6.5)

SYMPTOMS

When using trace flag 4032 to trace incoming queries to SQL Server, RPC events do not document the process id (spid) or the time that the event occurred.

WORKAROUND

Use the SQL Trace utility, which will document this information.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

With the 4032 trace flag enabled, RPC events are normally documented as "EXECRPC" in the errorlog. ODBC clients and DB-Library clients (that use the stored procedure functions) create RPC events instead of Language events.

Additional query words: execrpc langexec sqltrace
Keywords : kbbug6.50 kbusage SSrvGen SSrvLock
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.