KB4230516 - FIX: A memory assertion failure occurs, and the server can't make new connections in SQL Server

Applies To

SQL Server 2017 Developer SQL Server 2017 Enterprise SQL Server 2017 Enterprise Core SQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

When you run an instance of Microsoft SQL Server, you receive the following memory assertion failure:

Note

Comment: 'Stack Trace'
Comment: 'Location: lckmgr.cpp:10012
Expression: removedEntry != NULL
SPID: 23
Process ID: 3328'

After the memory assertion failure, the server is unable to make any new connections. Additionally, the server deadlocks the scheduler, and the instance of SQL Server has to be restarted.

Resolution

This fix is included in the following updates for SQL Server:

Cumulative Update 7 for SQL Server 2017

Cumulative Update 1 for SQL Server 2016 Service Pack 2

Note This fix addresses only the server deadlock issue that leaves the server unable to make any new connections.

About SQL Server builds

Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install:

The latest build for SQL Server 2017.

The latest build for SQL Server 2016.

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 standard terminology Microsoft uses to describe software updates.