Jump to content


marlonc1980

Link has Failed; Replicatión Secundary Site

Recommended Posts

Hello, thank you, your support I managed to learn enough of the tool.
Currently I have an environment; primary and several secondary site, now I lost the link replication with multiple servers, to run the replication analyzer tells me that there is a firewall, and that because of this there is no replication. and I have the firewall disabled validé; give ping and I connect with remote desktop computer correctly
The database is fine, no suspect has been apparently all is well.
================================================================
RCMCTRL.LOG site secundary.

 

*** [08001][26][Microsoft]
Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:56 4012 (0x0FAC)
*** [08001][233][Microsoft][sql Server Native Client 10.0]Shared Memory Provider: No hay ningún proceso en el otro extremo de la canalización. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:56 4012 (0x0FAC)
*** [08001][26][Microsoft][sql Server Native Client 10.0]Client unable to establish connection SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:57 4012 (0x0FAC)
*** [08001][233][Microsoft][sql Server Native Client 10.0]Client unable to establish connection due to prelogin failure SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:57 4012 (0x0FAC)
*** Failed to connect to the SQL Server. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:57 4012 (0x0FAC)
DrsSync thread failed to get a sql connection. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:57 4012 (0x0FAC)
DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:59 4016 (0x0FB0)
ERROR: Received unhandled SQL exception, printing info and throwing it again. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:59 4016 (0x0FB0)
ERROR: Exception message: [Error en el nivel de transporte al enviar la solicitud al servidor. (provider: Proveedor de TCP, error: 0 - Se ha forzado la interrupción de una conexión existente por el host remoto.)] SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:59 4016 (0x0FB0)
Failed to call ExecuteDrsActivationSproc. error = Unknown error 0x80131904 SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:53:59 4016 (0x0FB0)
DRS sync started. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:54:57 4012 (0x0FAC)
Wait for inbox notification timed out. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:38 4000 (0x0FA0)
Cleaning the RCM inbox if there are any *.RCM files for further change notifications.... SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:38 4000 (0x0FA0)
Initializing RCM. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 4000 (0x0FA0)
DRS change application started. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 2432 (0x0980)
Processing Replication SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 4000 (0x0FA0)
Launching 2 sprocs on queue ConfigMgrDRSQueue and 0 sprocs on queue ConfigMgrDRSSiteQueue. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 2432 (0x0980)
Running configuration EnsureServiceBrokerEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 4000 (0x0FA0)
Running configuration EnsureServiceBrokerQueuesAreEnabled. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 4000 (0x0FA0)
The asynchronous command finished with return message: [Error en el nivel del transporte al recibir los resultados del servidor. (provider: Proveedor de TCP, error: 0 - El nombre de red especificado ya no está disponible.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 2432 (0x0980)
The asynchronous command finished with return message: [Error en el nivel del transporte al recibir los resultados del servidor. (provider: Proveedor de TCP, error: 0 - El nombre de red especificado ya no está disponible.)]. SMS_REPLICATION_CONFIGURATION_MONITOR 14/01/2013 9:55:39 2432 (0x0980)
=========================
Here I give you part of the output of the analyzer
==================

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsSysCommitTabError SqlInstanceName="ServerPrimary.mydomain" ></IsSysCommitTabError>

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Verbose: 1 : The last time sys.syscommittab error was checked at 01/11/2013 11:13:00.

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Verbose: 1 : SQL's error log file for SQL instance ServerPrimary.mydomain is C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG.

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Information: 1 : Scanning SQL error log files for the string [3999].

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Verbose: 1 : Checking SQL error log file \\ServerPrimary.mydomain\C$\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG.

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Verbose: 1 : Done checking the file \\ServerPrimary.mydomain\C$\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG since all other lines in the file are earlier than last check date and time.

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Information: 1 : Running rule: <IsSysCommitTabError SqlInstanceName="Serversecundary.mydomain.com\CONFIGMGRSEC" ></IsSysCommitTabError>

1/14/2013 10:00:12 AM: ReplicationLinkAnalysis Verbose: 1 : The last time sys.syscommittab error was checked at 01/11/2013 11:13:00.

1/14/2013 10:00:13 AM: ReplicationLinkAnalysis Verbose: 1 : SQL's error log file for SQL instance Serversecundary.mydomain.com\CONFIGMGRSEC is c:\Program Files\Microsoft SQL Server\MSSQL10_50.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.

1/14/2013 10:00:14 AM: ReplicationLinkAnalysis Information: 1 : Scanning SQL error log files for the string [3999].

1/14/2013 10:00:14 AM: ReplicationLinkAnalysis Verbose: 1 : Checking SQL error log file \\Serversecundary.mydomain.com\c$\Program Files\Microsoft SQL Server\MSSQL10_50.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.

1/14/2013 10:00:14 AM: ReplicationLinkAnalysis Verbose: 1 : Checking SQL error log file \\Serversecundary.mydomain.com\c$\Program Files\Microsoft SQL Server\MSSQL10_50.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.1.

1/14/2013 10:00:14 AM: ReplicationLinkAnalysis Verbose: 1 : Checking SQL error log file \\Serversecundary.mydomain.com\c$\Program Files\Microsoft SQL Server\MSSQL10_50.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.2.

1/14/2013 10:00:14 AM: ReplicationLinkAnalysis Verbose: 1 : Done checking the file \\Serversecundary.mydomain.com\c$\Program Files\Microsoft SQL Server\MSSQL10_50.CONFIGMGRSEC\MSSQL\Log\ERRORLOG.2 since all other lines in the file are earlier than last check date and time.

 

=========================================================================

 

post-17189-0-44373200-1358177444_thumb.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.