When you run a full-text query that has the CONTAINS predicate, and the CONTAINS predicate also has the NEAR proximity term in SQL Server 2012, you receive the following error message:
Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Additionally, the following error message is logged in the SQL Server event log:
Date Time spid# Unknown,* EXEC [indexer].[BuildThreadSoftwareIndex] NULL Date Time spid# Unknown,* Input Buffer 114 bytes - Date Time spid# Unknown,* Access Violation occurred reading address 0000000000000038 Date Time spid# Unknown,* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION Date Time spid# Unknown,* Exception Address = 000007FFB8FBF1B0 Module(UNKNOWN+0000000000000000
This issue occurs because a defect in the full-text query pipeline.
Cumulative update information
Cumulative update package 3 for SQL Server 2012
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012, click the following article number to view the article in the Microsoft Knowledge Base:
Cumulative update 3 for SQL Server 2012
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 2012 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:
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to search for words close to another word with NEAR, go to the following MSDN website: