Article ID: 2591461 - Last Review: December 20, 2011 - Revision: 3.1

FIX: "Unexpected error from SE OLEDB interface" error when you run a full-text search query in SQL Server 2008 or in SQL Server 2008 R2

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Microsoft distributes Microsoft SQL Server 2008 Service Pack 1 (SP1) or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP1 or SQL Server 2008 R2 update release.

Back to the top

SYMPTOMS

When you run a full-text search query in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2, a SQL Server assertion failure might occur. Additionally, the following error is logged in the SQL Server error log and a mini dump file is generated in the SQL Server log folder if this issue occurs:

<Date> <Time> spid# * Location: ftcomoprowsetnew.cpp:199
<Date> <Time> spid# * Expression: (SUCCEEDED(hr))
<Date> <Time> spid# * Description: Unexpected error from SE OLEDB interface
<Date> <Time> spid# Error: 17065, Severity: 16, State: 1.
<Date> <Time> spid# SQL Server Assertion: File: <ftcomoprowsetnew.cpp>, line = 199 Failed Assertion = '(SUCCEEDED(hr))' Unexpected error from SE OLEDB interface. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:

2633145 (http://support.microsoft.com/kb/2633145/ ) Cumulative Update package 11 for SQL Server 2008 R2

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 2008 R2 fix release. We recommend 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:

981356 (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2633146 (http://support.microsoft.com/kb/2633146/ ) Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1

2567616 (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 7 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2617148 (http://support.microsoft.com/kb/2617148/LN/ ) Cumulative update package 7 for SQL Server 2008 Service Pack 2

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 2008 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:

2402659 (http://support.microsoft.com/kb/2402659/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative update package 16 for SQL Server 2008 SP1

The fix for this issue was first released in cumulative update package 16. For more information about how to obtain this cumulative update package for SQL Server 2008 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2582282 (http://support.microsoft.com/kb/2582282/ ) Cumulative update package 16 for SQL Server 2008 Service Pack 1

Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP1 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

970365 (http://support.microsoft.com/kb/970365/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released

Back to the top