In certain rare conditions, the Administration Service may fail to properly configure a Subscriber database server:
1) The New Replication Partner wizard in the Active Roles console reports that the operation is completed successfully, but the Subscriber database server configured by the wizard remains in standalone state and the Publisher database server does not recognize the newly configured Subscriber (the Subscriber's status on the Publisher is indicated as "unknown").
2) The Active Roles Admin Service event log contains a "ReplPartnerPolicy failed" error event in this case. Data synchronization between the Publisher and the newly configured Subscriber does not occur.
This is a known issue (TF0038646).
Please refer to the product's release notes (search for Issue ID: 38646):
Use the instructions that follow to delete the failed Subscriber record from the Publisher's database, and then use the New Replication Partner wizard in the Active Roles console to add the Subscriber again.
1) To delete the failed Subscriber record, run the following SQL query against the Active Roles database on the Publisher database server (before running the query, replace the <databasename> and <servername> placeholders with the name of the failed Subscriber database and the name of the SQL Server instance that hosts the failed Subscriber database, respectively):
delete from tblReplication where edsaSQLAlias = N'<servername>' and edsaDatabaseName = N'<databasename>'