KB4512151 - FIX: Access Violation occurs when you use LOG function with a remote query in SQL Server 2016 and 2017

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now


Consider the following scenario:

  • You create a linked server in Microsoft SQL Server 2016 or 2017 that points to a remote instance of SQL Server 2012 or later versions.

  • You want to use the LOG() function without explicitly specifying the logarithm base (to compute a natural algorithm).

When you run a query that calls LOG() with an argument referencing a remote table, then an Access Violation error may occur under certain conditions (For example: If your query uses UNION and an aggregate function such as SUM()).

Additionally, a dump file is generated on the local instance.

Msg 596, Level 21, State 1, Line LineNumber

Cannot continue the execution because the session is in the kill state.

Msg 0, Level 20, State 0, Line LineNumber

A severe error occurred on the current command.  The results, if any, should be discarded.


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


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

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:


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.