Symptoms
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)
Resolution
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
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 2017
Latest cumulative update for SQL Server 2016
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology Microsoft uses to describe software updates.
