none
Secondary site cannot get SQL certificate from parent RRS feed

  • Question

  • I didn't find any answers from the related topics. So I have this issue in the hman.log. I have reinstall this server. Tried to install on a new server but I get this same issue. I am not sure where to go anymore. Please help

    hman.log on child says

    Cannot get SQL Certificate from site xxx

    CheckParentSQLServerCertificate: Failed to get SQL certificate for site XXX

    Sender on child

    Registry indicates no outbox for the sender to scan

    We have 0 active connections

    Replmgr on child

    Did not find any replication files

    Wednesday, September 19, 2012 4:51 PM

Answers

  • 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.



    Friday, September 21, 2012 6:31 AM

All replies

  • What about replmgr.log, sender.log and rcmctrl.log on the parent site?

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, September 20, 2012 6:33 AM
  • 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.



    Friday, September 21, 2012 6:31 AM
  • Same problem here. Ports are fine.

    I get this error on almost every secondary site I install. Any ideas?

    Saturday, October 20, 2012 9:35 AM
  • I also had same issue on two secondary servers and was able to fix it by manually synch between primary and secondary(server which i had issue).

    to re-synch manually between primary and secondary use stored procedure as shown below...I executed below command from primary database.As soon a executed below command replication started between primary and secondary and issue got fixed.

    Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'


    verification

    • Proposed as answer by ihaa Wednesday, March 27, 2013 1:03 PM
    Wednesday, March 27, 2013 12:42 PM
  • Hi,

    This sounds like the issue I am seeing also. See my thread.

    Are you also able to run 'Replication Link Analyzer' from Monitoring, Database Replication?


    Wednesday, March 27, 2013 1:08 PM
  • I also had same issue on two secondary servers and was able to fix it by manually synch between primary and secondary(server which i had issue).

    to re-synch manually between primary and secondary use stored procedure as shown below...I executed below command from primary database.As soon a executed below command replication started between primary and secondary and issue got fixed.

    Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'


    verification

    Hi,

    Can you confirm if above is correct and command line should be "Exec spDrsSendSubscriptionInvalid 'Secondary Site Code', 'Primary Site Code', 'Configuration Data'" ?

    Wednesday, March 27, 2013 1:14 PM
  • Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'
    [...]
    Can you confirm if above is correct and command line should be "Exec spDrsSendSubscriptionInvalid 'Secondary Site Code', 'Primary Site Code', 'Configuration Data'" ?


    Looks identical (and valid) to me.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, March 27, 2013 1:28 PM
  • yes...i used the below command and was able to fix the issue 

    example - >  Exec spDrsSendSubscriptionInvalid 'SE1','PR1','configuration data'

    SE1 is my secondary site code and PR1 is my primary site code.


    verification

    Wednesday, March 27, 2013 6:55 PM
  • I get  this error with that.

    ERROR Sending SSB Message from: ConfigMgrRCM_SiteP01 to ConfigMgrRCM_SiteS05 SQL Error: 50000 SQL Message: ERROR 50000, Level 16, State 1, Procedure spGetSSBDialogHandle, Line 58, Message: Route is not defined for target site with service name ConfigMgrRCM_SiteS05.

    Msg 50000, Level 16, State 1, Procedure spRethrowError, Line 42

    ERROR 50000, Level 16, State 1, Procedure spRethrowError, Line 42, Message: ERROR 50000, Level 16, State 1, Procedure spGetSSBDialogHandle, Line 58, Message: Route is not defined for target site with service name ConfigMgrRCM_SiteS05.

    (1 row(s) affected)


    Monday, April 22, 2013 2:59 PM
  • can you post the command which you  are trying to execute..?

    verification

    Monday, April 22, 2013 3:58 PM
  • Monday, April 22, 2013 4:03 PM
  • I have the same problem.

    and secondary servers status remains as pending on the primary server

    Monday, April 29, 2013 2:18 PM
  • looks interesting.... beacuse i am able to run the command without any errors.


    verification

    Tuesday, April 30, 2013 9:46 AM
  • you have to monitor the logs mentioned after having run this command.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 30, 2013 10:02 AM
  • I was having the same issues with my first two Secondary Sites.  Both failed the prereqs and I had to do a retry install due to IIS components not being automatically installed .  The third 2ndary site went in with out a hitch, but I preconfigured the IIS components ahead of time -  so I attribute it to the retry install.

    I tried the sql script "Exec spDrsSendSubscriptionInvalid 'YXZ,'ABC','configuration data'" with no luck too- same error as as jamicon.  So I went the route of deinstalling the 2ndary site via ARP on the 2ndary site server and then deleted it from the 2012 CM console.  Reinstalled with new site codes and all went through and both problematic sites are now on line.

    Monday, August 19, 2013 4:54 PM
  • Have seen this issue a couple of times and running the following query have worked for me: Exec spDrsSendSubscriptionInvalid "SEC","PRI","configuration data" 

    Marius A. Skovli | MCP/MCTS/MCITP | Twitter: @mariusskovli

    Thursday, September 26, 2013 7:06 PM
  • I had the same issue. Ended up being a firewall issue where the secondary site sql could not connect over the service broker port to the primary site server. Using telnet and PortQuery Utility to verify communication, issue was then resolved.
    Friday, September 11, 2015 7:10 PM
  • I also had the same issue. Tried the above command but didn't help so I reinstall the site with new site code and solve the issue.
    Wednesday, August 17, 2016 10:39 AM