Microsoft KB Archive/165389

= FIX: Spid Missing with Trace Flag 4032 on RPC Events =

Article ID: 165389

Article Last Modified on 10/3/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q165389



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: kbbug kbfix kbusage KB165389

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.