locked
Database Replication Link Failed RRS feed

  • Question

  • We recently moved our Primary site from a "development" to a "production" box. When we did this, our database link has failed. I've run the "Replication Link Analyser" and here are the results:

    6/18/2012 9:39:54 AM: ReplicationLinkAnalysis Information: 1 : Initializing replication link analysis engine...
    6/18/2012 9:39:54 AM: ReplicationLinkAnalysis Information: 1 : Checking registry access to MYSERVER.mydomain.com.
    6/18/2012 9:39:54 AM: ReplicationLinkAnalysis Information: 1 : Checking registry access to MYSERVER.mydomain.com.
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Writing certificate for MYSERVER.mydomain.com in the certificate store.
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Writing certificate for MYSERVER.mydomain.com in the certificate store.
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : The certificate for MYSERVER.mydomain.com already exist in the cert store
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Checking if SQL service is running on MYSERVER.mydomain.com.
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsServiceRunning serviceName="MSSQLSERVER" serverName="MYSERVER.mydomain.com"  ></IsServiceRunning>
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Checking if SQL service is running on MYSERVER.mydomain.com\CONFIGMGRSEC.
    6/18/2012 9:39:55 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsServiceRunning serviceName="MSSQL$CONFIGMGRSEC" serverName="MYSERVER.mydomain.com"  ></IsServiceRunning>
    6/18/2012 9:40:16 AM: ReplicationLinkAnalysis Verbose: 1 : Connection string = Data Source=(local),1433;Initial Catalog=CM_BHM;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name=REPLICATION_LINK_ANALYZER.
    6/18/2012 9:40:16 AM: ReplicationLinkAnalysis Verbose: 1 : Created new sqlConnection to (local)
    6/18/2012 9:40:16 AM: ReplicationLinkAnalysis Information: 1 : SQL server MYSERVER.mydomain.com\CONFIGMGRSEC is using dynamic ports. Using port number 49454 to get SQL connection.
    6/18/2012 9:40:16 AM: ReplicationLinkAnalysis Verbose: 1 : Connection string = Data Source=MYSERVER.mydomain.com\CONFIGMGRSEC,49454;Initial Catalog=CM_ATL;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name=REPLICATION_LINK_ANALYZER.
    6/18/2012 9:40:38 AM: ReplicationLinkAnalysis Error: 1 : A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
    6/18/2012 9:40:38 AM: ReplicationLinkAnalysis Error: 1 : System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.SqlConnectionBuilder.GetSqlConnection(String sqlServerName, String sqlInstanceAndDatabaseName, String applicationName, SqlConnectionSecurityLevel securityLevel)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.SqlConnectionBuilder.GetSqlConnection(String siteServerName, String applicationName, Boolean forceEncryptedAndSecureConnection)
       at Microsoft.ConfigurationManager.ReplicationLinkAnalyzer.ReplicationLinkAnalysisEngine.Initialize()
    6/18/2012 9:40:38 AM: ReplicationLinkAnalysis Error: 1 : Failed to get SQL connection to MYSERVER.mydomain.com\CONFIGMGRSEC.
    6/18/2012 9:40:38 AM: ReplicationLinkAnalysis Error: 1 : Failed to initialize the link analysis engine.
    6/18/2012 9:40:38 AM: ReplicationLinkAnalysis Information: 1 : Completed replication link analysis thread.
    

    I noticed that the output suggusts there is an issue with connecting to the secondary site database, however, I am able to directly access this database through SQL Server Management studio from the primary site.

    I should note that everything was working as expected before we moved the server.



    Monday, June 18, 2012 2:44 PM

Answers

  • Sorry if this is late.  Looks like there may be an issue with permissions or the firewall from the target machine to the sql machine.  I suggest checking the Hman status messages under Component Status on the afflicted sites.  That will tell you if it's a firewall issue or not.  Finally you should double check that the Primary machine has permissions on the secondary sites.

    Chidozie Nwobilor

    Friday, September 7, 2012 5:46 PM

All replies

  • We recently moved our Primary site from a "development" to a "production" box. When we did this, our database link has failed.

    What have you done exactly? Have you also had a look at rcmctrl.log?

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

    Monday, June 18, 2012 2:53 PM
  • I'm with Torsten: please define "moved".

    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Monday, June 18, 2012 3:28 PM
  • Torsten,

    Our entire instance of CM 2012 was installed in a virtual environment. We simply moved the Primary site VHD to a new host. The following is the output of the rcmctrl.log file starting with today's date.

    http://sdrv.ms/Pc78mv


    • Edited by hhancock Monday, June 18, 2012 3:50 PM
    Monday, June 18, 2012 3:45 PM
  • Is your SQL server remote or local?

    Based on the above log its remote and connectivity has been interrupted: "A network-related or instance-specific error occurred while establishing a connection to SQL Server."

    Have you verified name resolution and connectivity to the SQL server?


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Monday, June 18, 2012 3:48 PM
  • Jason,

    To answer your question, yes. I am able to connect to the SQL instances (secondary sites) from SQL Management Studio on the primary site.

    Any other suggestions?


    • Edited by hhancock Monday, June 18, 2012 6:29 PM
    Monday, June 18, 2012 3:51 PM
  • Site Status

    According to the site status, everything is "OK." That includes the Site database server on the secondary sites. Why am I still receiving a database link error then? I also noticed a few errors on the SMS_MP_CONTROL_MANAGER component. Specifically, error 5420, Management Point encountered an error when connecting to the database CM_BHM on SQL Server MYSERVER.myserver.com. The OLEDB error code was 0x80004005.

    Replication Link Analyzer



    • Edited by hhancock Monday, June 18, 2012 8:22 PM
    Monday, June 18, 2012 7:48 PM
  • Anyone?
    Monday, June 25, 2012 7:07 PM
  • Sorry if this is late.  Looks like there may be an issue with permissions or the firewall from the target machine to the sql machine.  I suggest checking the Hman status messages under Component Status on the afflicted sites.  That will tell you if it's a firewall issue or not.  Finally you should double check that the Primary machine has permissions on the secondary sites.

    Chidozie Nwobilor

    Friday, September 7, 2012 5:46 PM