BugZero found this defect 1317 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
6/2/2022
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 2017 on Windows
build lower than 14.0.3238.1
14.0.3238.1
Assume that you have Microsoft SQL Server 2016 or 2017 installed on an Azure virtual machine (VM) whose name is not spelled as all uppercase letters. After you restart the SQL Server service, you notice that peer-to-peer replication fails. Additionally, you may receive an error message that resembles the following: No peers were found for Production. If you encounter this error when executing the stored procedure sp_requestpeerresponse, verify that subscriptions have been created before attempting to call the procedure again. If you encounter this error in other circumstances, contact Customer Support Services. (Source: MSSQLServer, Error number: 20807)
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 17 for SQL Server 2017 Cumulative Update 8 for SQL Server 2016 SP2 Cumulative update 12 for SQL Server 2016 SP1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.