FIX: Fatal error when a natively compiled stored procedure is executed to access memory-optimized tables in SQL Server 2017

Applies to: SQL Server 2017 Developer LinuxSQL Server 2017 Developer on WindowsSQL Server 2017 Enterprise on Windows

Symptoms


Assume that you use in-memory Online Transaction Processing (OLTP) in SQL Server 2017 on Linux or Windows. When you execute a natively compiled stored procedure to access memory-optimized tables, the execution fails, and you receive an error message that resembles the following:

System.InvalidOperationException: Internal connection fatal error. Error state: 15, Token : 0
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryCloseInternal(Boolean closeReader)
   at System.Data.SqlClient.SqlDataReader.Close()
   at System.Data.Common.DbDataReader.Dispose(Boolean disposing)
   at System.Data.Common.DbDataReader.Dispose()

Additionally, a dump file is generated by SQL Server.

Resolution


This issue is fixed in the following cumulative update for SQL Server:

       Cumulative Update 2 for SQL Server 2017

Status


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

References


Learn about the terminology that Microsoft uses to describe software updates.