There are two related scenarios that can trigger these specific error messages. The first is attempting to configure an On-Premise
Microsoft SQL Server database with a Transactional Replication Publisher to an Azure SQL Database Subscriber. The second is with an
already configured setup and during a planned or unplaned fail-over of a WFSC(Windows Server Failover Cluster) from one Node to another
where the Nodes do not have the same engine version. The root cause of both is the On-Premise SQL Server is not at the minimal required
level to connect with an Azure SQL Database (SaaS).
The exact error messages are:
1. "The process could not connect to Subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL20084)"
2. "Cannot open server requested by the login. The login failed. (Source: MSSQLServer, Error number: 40532)"
The solution is to upgrade the On-Premise SQL Server to reach the required version, then connectivity to Microsoft Azure will
be established.
Resources:
Replication to SQL Database
|
|
|
|
|
|