locked
Link Failed - Check Network Connection RRS feed

  • Question

  • This past Monday, one of my sccm 2012 secondary site servers had to be taken offline because the building lost power for the day.  Since then, the db link state (monitoring -> Database Replication) for that secondary site has showed failed, even though the site has been back online for over 24 hours. 

    When I run the replication link analyzer, I get this: 
    Connection failure detected between SCCM-CP1.hw.local and the SQL Server SCCM-PA2.hw.local\CONFIGMGRSEC.  Check network and firewall settings between these computers.

    EDIT:  I forgot to mention the obvious: the network connection between the two sites is up and in excellent condition

    When I view the replication status for that link, everything is green on the parent site tab, and ? on the child site tab.  The summary tab shows the following: 

    Site Replication Status
    Parent Site:  CP1
    Parent Site State:  Replication Active
    Child Site:  PA2
    Child Site State:  Replication Active

    Global Data Replication Status
    Parent Site to Child Site Global State:  Link Failed
    Parent Site to Child Site Global Synchronization Time:  5/7/2012 10:32 AM
    Child Site to Parent Site Global State:  Link Failed
    Last Synchronization Time:  5/7/2012 9:10 AM
    Global Data Initialization Percentage:  100%

    Site Data Replication Status
    Child Site to Parent Site State:  Not Applicable
    Child Site to Parent Site Synchronization Time:


    • Edited by Kenneth Merenda Wednesday, May 9, 2012 4:21 PM Add network status
    Wednesday, May 9, 2012 4:20 PM

Answers

  • A simple restart of both servers seems to have resolved the issue.
    Wednesday, May 9, 2012 4:24 PM

All replies

  • A simple restart of both servers seems to have resolved the issue.
    Wednesday, May 9, 2012 4:24 PM
  • Mine has been doing the same thing, however, restarting the servers did NOT solve my issue.
    Monday, June 25, 2012 8:14 PM
  • Mine has been doing the same thing, however, restarting the servers did NOT solve my issue.

    I find my self in the same situation.

    May i ask, what did solve your problem.


    gfraetis

    Saturday, April 11, 2015 6:47 PM