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 | 13472695
KB4563348 - After upgrading SQL Server 2017 Distributor to SQL Server 2019, transactional push replication fails when subscriber is using non-default port - Microsoft Support
Last update date:
6/20/2023
Affected products:
SQL Server 2019 on Windows
Affected releases:
build lower than 15.0.4043.16
Fixed releases:
15.0.4043.16
Description:
Symptoms
Assume that you upgrade the Remote Distributor running on SQL Server 2017 to SQL Server 2019 with any Subscriber that's not using a default port number 1433. In this situation, you may notice that the Distribution Agent fails to connect to the Subscriber after the upgrade. Additionally, you may receive the following error messages: Msg 20032, Level 16, State 1, Procedure ProcedureName, Line LineNumber [Batch Start Line LineNumber ] 'ProcedureName' is not defined as a Subscriber for 'ProcedureName'. Msg 14070, Level 16, State 1, Procedure ProcedureName, Line LineNumber [Batch Start Line LineNumber ] Could not update the distribution database subscription table. The subscription status could not be changed. Msg 14057, Level 16, State 1, Procedure ProcedureName, Line LineNumber [Batch Start Line LineNumber ] The subscription could not be created. Msg 20021, Level 16, State 1, Procedure ProcedureName, Line LineNumber [Batch Start Line LineNumber ] The subscription could not be found.
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 update for SQL Server: Cumulative Update 5 for SQL Server 2019 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 2019
More information
If you remove all the subscribers after upgrading distributor to SQL Server 2019, and then try to create new subscription to the same subscriber, it may fail. To fix this behavior, delete the linked server entry for subscriber in the format "servername,port", and delete the entry of subscriber in format "servername,port" from [distribution].[dbo].[MSreplservers].
References
Learn about the terminology that Microsoft uses to describe software updates.
