Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10691456
KB4023926 - FIX: Unable to drop stored procedure execution article from P2P publication in SQL Server - Microsoft Support
Last update date:
7/21/2023
Affected products:
SQL Server 2014 Developer - duplicate (do not use)
SQL Server 2014 Enterprise - duplicate (do not use)
SQL Server 2014 Standard - duplicate (do not use)
SQL Server 2014 Service Pack 2 - duplicate (do not use)
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)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
Assume that you create a Peer-to-Peer (P2P) publication in Microsoft SQL Server and add a stored procedure execution article to it. When the stored procedure is executed at the Publisher, replication executes the corresponding procedure at the Subscriber. However, when you try to drop the stored procedure execution article, you may receive an error message that resembles the following: Cannot drop article ProcedureName. An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) Cannot continue the execution because the session is in the kill state. A severe error occurred on the current command. The results, if any, should be discarded. Changed database context to DatabaseName. (Microsoft SQL Server, Error: 596)
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 RTM Cumulative Update 5 for SQL Server 2016 SP1 Cumulative Update 6 for SQL Server 2014 SP2
