I have a link between a Primary Site and Secondary Site that is in Link Failed state. When I run the Replication Link Analyzer I get a message that says "Issues Detected" but underneath "Analysis and remediation summary" I see all green check marks.

The View Report button takes me to an .htm file where every test has passed.

The View Log button takes me to the ReplicationLinkAnalysis.log file where I see several error messages.

6/24/2015 3:34:34 PM: ReplicationLinkAnalysis Error: 1 : Failed to get access to service control manager at SECSITE.DOMAIN.biz. Exception: [Access is denied, ErrorCode: -2147467259].

6/24/2015 3:34:40 PM: ReplicationLinkAnalysis Error: 1 : Failed to get access to file share \\SISADB007.siigroup.biz\SMS_SITE. Exception: [Access to the path '\\SECSITE.DOMAIN.biz\SMS_SITE\RLATestSiteToSiteConnectionT.txt' is denied.].

6/24/2015 3:35:16 PM: ReplicationLinkAnalysis Error: 1 : Failed to execute WMI query on SECSITE.DOMAIN.biz. Exception: [Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))].

Are these access denied messages preventing the Secondary Site server from communicating with the primary site server? Why would this suddenly begin to fail? Why is the RLA prompting me for a username and password when it runs? That has never happened before.

Hi,

Did you figure this out?

Tips for troubleshooting SC 2012 Configuration Manager Data Replication Service (DRS)

http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx

Hi,

Did you figure this out?

Tips for troubleshooting SC 2012 Configuration Manager Data Replication Service (DRS)

http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx

I was unable to fix the Secondary Site. I deleted it from the hierarchy.

Deleting the Secondary Site from the hierarchy and replacing it with a multiple distribution points is not a fix for a broken database replication link.

Why didn't you add a new secondly site?

Did you contact Microsoft support over this issue?

What does the secondary site give you that the DPs don't?

I agree with Garth on this.

Generally in ConfigMgr 2012 Secondary sites are not really necessary anymore and there are very few justifications for setting up a secondary site now.

The following link goes into some reasons:
https://technet.microsoft.com/en-au/library/gg712681.aspx#BKMK_ChooseSecondary

If all you need at the remote site is content delivery then the distribution point role will satisfy this requirement.

Deleting the Secondary Site from the hierarchy and replacing it with a multiple distribution points is not a fix for a broken database replication link.

Why didn't you add a new secondly site?

Did you contact Microsoft support over this issue?

What does the secondary site give you that the DPs

I agree with Garth on this.

Generally in ConfigMgr 2012 Secondary sites are not really necessary anymore and there are very few justifications for setting up a secondary site now.

The following link goes into some reasons:
https://technet.microsoft.com/en-au/library/gg712681.aspx#BKMK_ChooseSecondary

If all you need at the remote site is content delivery then the distribution point role will satisfy this requir

If low bandwith was a concern you could use a normal DP at the main remote site and use Pull Distribution points on the other satellite sites specifying the main remote site as their source.

This solution would then mean that the package was only transferred once from your primary site and the other DP's would pull from the main remote site.

Pull distribution points were introduced in SP1
http://blogs.technet.com/b/configmgrteam/archive/2013/06/06/introducing-the-pull-distribution-points.as