August 25, 2016 at 8:33 pm
After I performed mirroring failover , my outgoing replications from the database started failing after sometime of successful run with the error message
Error messages:
Invalid connection string attributeTCP Provider: The wait operation timed out.A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.TCP Provider: The wait operation timed out.A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (Source: MSSQL_REPL, Error number: MSSQL_REPL20015)
Get help: http://help/MSSQL_REPL20015
Invalid connection string attributeTCP Provider: The wait operation timed out.A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.TCP Provider: The wait operation timed out.A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Get help: http://help/MSSQL_REPL22037
Later I stopped and started synchronization , it started working fine
Can help me what happened in the middle which caused the transactional replication to start failing suddenly ? How to check more on this
August 27, 2016 at 12:04 am
Taking the errors at face value - replication was experiencing a networking (not a SQL Server) concern, perhaps rooted in name resolution. There are better forums for T-shooting a networking concern than this one :).
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply