Summary
In SQL Server 2012,2014 or 2016, when documents are too large for Full-Text Search indexing, an exception that resembles the following is logged in the SQL Server error log, and a dump file is generated. Additionally, full-text queries may return incorrect results.
Note
ex_raise2: Exception raised, major=300, minor=45, state=53, severity=17
Note Support for Full-Text Search indexing on large documents that exceed word position values greater than 4,294,966,016 is not added in this update.
After you install this update and SQL Server indexes documents that are too large for Full-Text Search indexing, the documents are skipped, and SQL Server generates an error message resembling the following in the Full-Text Search error log instead of throwing exceptions and generating file dumps.
Note
Error '0x8004fd0a: Occurrence counter overflow, document is not indexed.' occurred during full-text index population for table or indexed view object_name (table or indexed view ID object_id, database ID database_id), full-text key value full-text_key_value. Failed to index the row.
Resolution
This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 5 for SQL Server 2016 RTM
Cumulative Update 2 for SQL Server 2016 SP1
Cumulative Update 5 for SQL Server 2014 SP2
Cumulative Update 11 for SQL Server 2014 Service Pack 1
Cumulative Update 8 for SQL Server 2012 SP3
About cumulative updates for SQL Server
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Latest cumulative update for SQL Server 2016
Latest cumulative update for SQL Server 2014
Latest cumulative update for SQL Server 2012
References
Learn about the terminology Microsoft uses to describe software updates.