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

Applies to: SQL Server 2016 Service Pack 2SQL Server 2016 DeveloperSQL Server 2016 Enterprise

Symptoms


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.

Status


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

Resolution


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:

References


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