KB3097972 - FIX: Error when your stored procedure calls another stored procedure on a linked server in SQL Server 2014

Applies To
SQL Server 2014 Developer - duplicate (do not use) SQL Server 2014 Enterprise - duplicate (do not use) SQL Server 2014 Standard - duplicate (do not use)

Symptoms

Assume that you create a linked server to an instance of Microsoft SQL Server 2014 Service Pack 1 (SP1). When you run a stored procedure that calls another stored procedure on the linked server, and you pass a large object as the input parameter, the query fails. Additionally, you receive the following error message:

Note

Error: 17065, Severity: 16, State: 1.
SQL Server Assertion: File:< tmpilb.cpp>, line = 3280 Failed Assertion = 'fFalse' Release. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.

Resolution

Hotfix information

This hotfix is included in the following cumulative update of SQL Server 2014 SP1:

          

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 2014
      

Hotfixes that are included in this package

VSTS bug number KB article number Description
5699529 3097972 FIX: Error when your stored procedure calls another stored procedure on a linked server in SQL Server 2014
5951292 3106976 FIX: An access violation occurs when you use the TDE and BPE features in SQL Server 2014
5952334 3074434 FIX: Out of memory error when the virtual address space of the SQL Server process is very low on available memory

PrerequisitesYou must have SQL Server 2014 SP1 applied before you can install this hotfix.

Registry informationTo use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirementYou may have to restart the computer after you apply this hotfix.

Hotfix replacement information This hotfix doesn't replace a previously released hotfix.

Status

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