FIX: "SQL Server is terminating this process" error message when the "OLEDB Call Event" event is captured by using SQL Server Profiler or a server-side trace in SQL Server 2005

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

Symptoms

Assume that you have an application that uses an OLE DB provider to connect to an instance of Microsoft SQL Server 2005. You use SQL Server Profiler or a server-side trace to capture the OLEDB Call Event event for the instance of SQL Server 2005. In this situation, an access violation exception occurs and you receive the following error message. Additionally, the instance may crash.

2010-06-24 19:02:59.50 spid64 SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2010-06-24 19:02:59.50 spid64 * *******************************************************************************
2010-06-24 19:02:59.50 spid64 * BEGIN STACK DUMP:
2010-06-24 19:02:59.50 spid64 * Exception Address = 0000000002716AF1 Module(sqlservr+0000000001716AF1)
2010-06-24 19:02:59.50 spid64 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
2010-06-24 19:02:59.50 spid64 * Access Violation occurred reading address 0000000000000000

Note For more information about the OLEDB Call Event event, see the following table:

Event numberEvent nameDescription
119OLEDB Call EventOccurs when OLE DB provider calls are made for distributed queries and remote stored procedures.

Cause

This issue occurs because SQL Server 2005 tries to read an invalid address internally when the OLEDB Call Event event is being captured.

Resolution

SQL Server 2005 Service Pack 3

The fix for this issue was first released in Cumulative Update 13 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2438344 Cumulative update package 13 for SQL Server 2005 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 4

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 4. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2489409 Cumulative update package 2 for SQL Server 2005 Service Pack 4
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2485757 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 4 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 4 hotfix to an installation of SQL Server 2005 Service Pack 4. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Workaround

To work around this issue, do not capture the OLEDB Call Event event for the instance of SQL Server 2005.

References

For more information about sp_trace_setevent (Transact-SQL), visit the following Microsoft Developer Network (MSDN) website:For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:

935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Propiedades

Id. de artículo: 2475907 - Última revisión: 21 feb. 2011 - Revisión: 1

Comentarios