FIX: Spid Missing with Trace Flag 4032 on RPC Events

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          : kbusage SSrvGen SSrvLock kbbug6.50 
Version           : 6.5
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: April 9, 1999