Communication Link Failures

Question

Communication Link Failures

kylemkr85

Mr or Mrs. 500

Points: 501
More actions
April 22, 2013 at 10:25 am

#276803

Hello,
I am receiving Communication link failures in SQL which are causing my backups to fail. This has been occurring off and on throughout the week. I have attached the SQL log below. Has anyone had this issue before? What could be causing this? I run a two-node cluster with 3 instances on each node.
SQL Log
04/20/2013 20:07:04,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:04,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:04,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:07:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 20:05:58,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:04:52,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:04:52,,Error,[298] SQLServer Error: 10054<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:04:52,,Error,[298] SQLServer Error: 10054<c/> TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:03:02,,Warning,[396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
04/20/2013 16:03:02,,Warning,[408] SQL Server I_PDBMSZD is clustered - AutoRestart has been disabled
04/20/2013 16:03:01,,Information,[129] SQLAgent$I_PDBMSZD starting under Windows NT service control
04/20/2013 16:03:01,,Error,[364] The Messenger service has not been started - NetSend notifications will not be sent
04/20/2013 16:03:01,,Information,[432] There are 12 subsystems in the subsystems cache
04/20/2013 16:03:00,,Information,[339] Local computer is PDBMSZD running Windows NT 6.1 (7600)
04/20/2013 16:03:00,,Information,[310] 8 processor(s) and 64510 MB RAM detected
04/20/2013 16:03:00,,Information,[103] NetLib being used by driver is DBNETLIB.DLL; Local host server is PDBMSZD\I_PDBMSZD
04/20/2013 16:03:00,,Information,[102] SQL Server ODBC driver version 10.50.2500
04/20/2013 16:03:00,,Information,[101] SQL Server PDBMSZD\I_PDBMSZD version 10.50.2500 (0 connection limit)
04/20/2013 16:03:00,,Information,[100] Microsoft SQLServerAgent version 10.50.2500.0 ((Unknown) unicode retail build) : Process ID 19484
04/20/2013 16:02:49,,Information,[393] Waiting for SQL Server to recover databases...
04/20/2013 16:02:15,,Warning,[098] SQLServerAgent terminated (forcefully)
04/20/2013 16:02:14,,Error,[264] An attempt was made to send an email when no email session has been established
04/20/2013 16:02:03,,Warning,[188] Scheduler engine timed out (after 15 seconds) waiting for 5 jobs(s) to stop
04/20/2013 16:01:48,,Error,[165] ODBC Error: 0<c/> SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
04/20/2013 16:01:47,,Error,[165] ODBC Error: 0<c/> SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
04/20/2013 16:01:47,,Error,[382] Logon to server 'PDBMSZD\I_PDBMSZD' failed (ConnSetJobCompletionState)
04/20/2013 16:01:47,,Error,[298] SQLServer Error: 65535<c/> 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. [SQLSTATE 08001]
04/20/2013 16:01:47,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00]
04/20/2013 16:01:47,,Error,[298] SQLServer Error: 65535<c/> SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
04/20/2013 16:01:47,,Error,[382] Logon to server 'PDBMSZD\I_PDBMSZD' failed (ConnLogJobHistory)
04/20/2013 16:01:47,,Error,[298] SQLServer Error: 65535<c/> 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. [SQLSTATE 08001]
04/20/2013 16:01:47,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00]
04/20/2013 16:01:47,,Error,[298] SQLServer Error: 65535<c/> SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. [SQLSTATE 08001]
04/20/2013 16:01:47,,Information,[131] SQLAgent$I_PDBMSZD service stopping due to a stop request from a user<c/> process<c/> or the OS...
04/20/2013 16:01:36,,Error,[382] Logon to server 'PDBMSZD\I_PDBMSZD' failed (ConnUpdateRunRequestedJobActivity)
04/20/2013 16:01:36,,Error,[298] SQLServer Error: 258<c/> Unable to complete login process due to delay in prelogin response [SQLSTATE 08001]
04/20/2013 16:01:36,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00]
04/20/2013 16:01:30,,Error,[298] SQLServer Error: 258<c/> TCP Provider: Timeout error [258]. [SQLSTATE 08001]
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 10004<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 10054<c/> Communication link failure [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:01:03,,Error,[298] SQLServer Error: 10054<c/> TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01] (LogToTableWrite)
04/20/2013 16:00:55,,Error,[298] SQLServer Error: 16389<c/> Communication link failure [SQLSTATE 08S01]
04/20/2013 16:00:55,,Error,[298] SQLServer Error: 121<c/> Communication link failure [SQLSTATE 08S01]
04/20/2013 16:00:55,,Error,[298] SQLServer Error: 121<c/> TCP Provider: The semaphore timeout period has expired. [SQLSTATE 08S01]

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply

dbafromthecold@gmail.com SSChampion Points: 10160 More actions · Answer 1

Hello,

Just from having a quick look at the error log, have you been getting failovers during the week? It would explain why the communication errors are there and why the backups have been failing?

What has been happening with the cluster?

Andrew