I had the exact same issue happen to me few days ago and finally had to open a case with MS. Something is wrong with the sql server service broker and the way certificates are sent.
First make sure you can telnet to 1433 and 4022 from Primary to Secondary and vice versa. If thats working fine, your sql port communication is fine.
Try removing the secondary site and adding it back. If the option to remove is not available in console, you will have to delete the secondary and then manually uninstall the secondary site. Try adding the secondary back again. Keen an eye on hman.log.
If same error,"CheckParentSQLServerCertificate" comes back, one last thing you can try is re installing the
secondary site server with a different site code. (this i have heard worked for some one, true story ;))
I never was able to resolve this issue and wasted almost a month. Finally dropped the idea of installing a secondary and went with standalone DP's,MP's etc.
If the different site code trick works for you, then this could be a possible bug. Keep posted on how that goes. best of luck my friend.
-
Marked as answer by
Robert Marshall - MVPMVP, Moderator
Saturday, June 01, 2013 6:15 PM