BUG: Running SQL Trace with RPC Calls and sp_OA May Cause Access Violation

• Microsoft SQL Server version 6.5

SYMPTOMS

SQL Server may experience an Open Data Services (ODS) exception error and/or exit if an application is making remote procedure calls (RPCs) to stored procedures where the stored procedures are subsequently making calls to the sp_OA* stored procedures (for example, sp_OACreate) while SQL Trace is running.

WORKAROUND

To work around this problem, do either of the following:

• If you must use RPC calls to SQL Server and you also need to make sp_OA* calls inside stored procedures, limit the use of SQL Trace on your production server.
  
  -or-



• Instead of making an RPC call to SQL Server to invoke the stored procedure containing the sp_OA* calls, make direct calls to the stored procedure using normal Transact-SQL. If you are using ADO, do not use the AppendParameter method of the ADODB.Command object. For DB-Library applications, call dbcmd instead of dbrpcexec.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.

MORE INFORMATION

This behavior is very specific to the scenario described in the SYMPTOMS section of this article. To further clarify this problem, all of the following conditions must be present to cause this behavior:

• The application must be making RPC calls to SQL Server. RPC calls are special calls to SQL Server that bypass the Transact-SQL parser on the server. From DB-Library, you would use dbrpcexec(); ODBC would use the "{call <name>}" syntax; ADO would use the ADODB.Command object and use the CreateParameter to bind parameters to the Command object.



• The stored procedure being invoked must be making calls to any of the sp_OA* internal stored procedures. Typically, this will be sp_OACreate.



• SQL Trace must be running on the server while these calls are being made.

Additional query words: COM xp_sqltrace st proc sproc dblib db-lib

Keywords : kbbug6.50
Version : winnt:6.5
Platform : winnt
Issue type : kbbug