Communication Link failure

Hello,
Sometimes my application accessing SQL Server via ODBC is giving an error message "Communication link failure".
The network and server looks fine, but I'am still getting it time to time.
Please recommend possible reasons and solutions.
Thanks indvance.We has some unnoticed unstable connections very difficult to find because NT retried to connect without warning (maybe just some lattency when you tried to access again a lan resource).
We checked with "ping -w5000 -t"
The problem was bad coupling male/female RJ45 connectors in some stations.

Hope this helps,
Csar.

Communication Link Failure

Why would we get a " Communication Link Failure "
I have seen " TimeOut Expired " and General Network Error and can
understand why we get those, but what about the one listed in subject
Any idea ?
Hi Hassan,
Did you ever find a solution to your problem? I had that same issue
today. I did some research and I found some FAQ that stating:
" Make sure that your largest column is the last column retuned. Make
sure that you do not have any columns returned after a text or an image
column"
I kind of don't fully understand it, but in my case.. I had some columns
will a NULL value at the end of the table. I moved them and it seemed
to fix my problem. Here's the site that I found:
http://www.15seconds.com/faq/ODBC/692.htm
Marc F.
Hassan wrote:
> Why would we get a " Communication Link Failure "
> I have seen " TimeOut Expired " and General Network Error and can
> understand why we get those, but what about the one listed in subject
> Any idea ?
>

Communication Link Failure

SQL 7, SP4
windows NT 4, SP6
SQL Server Agent jobs are failing, history
reports "ConnectionRead (SQLState 01000) Message 0
Communication Link Failure (SQL Sate 08S01) (Error 10004)
Jobs have been working fine until yesterday.
DBCC checkdb master, msdb, no errors reported.
I can backup the databases through a third party
application though, so what's up with the ODBC error
message reported by the job history?
Internet searching no help.
Need someone to come to my rescue!"Mary" <Mary_Scheffler@.urscorp.com> wrote in message
news:030e01c3fc16$dc082ff0$3a01280a@.phx.gbl...
> SQL 7, SP4
> windows NT 4, SP6
> SQL Server Agent jobs are failing, history
> reports "ConnectionRead (SQLState 01000) Message 0
> Communication Link Failure (SQL Sate 08S01) (Error 10004)
> Jobs have been working fine until yesterday.
> DBCC checkdb master, msdb, no errors reported.
> I can backup the databases through a third party
> application though, so what's up with the ODBC error
> message reported by the job history?
Check this out -- may be caused if there are pending transactions:
http://support.microsoft.com/defaul...kb;en-us;114630
Steve

Communication Link Failure

Thanks in advance for any help. I really appreciate it.
I am getting a strange error message when connecting to a single Sql Server
all of the sudden.
From enterprise manager the error is:
A connection could not be established to ServerName.
Reason: Communication link failure
Please verify Sql Server is running and check your Sql Server registration
properties (by right-clicking on the ServerName node) and try again.
From Query Analyzer the error is:
Unable to connect to server ServerName
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC Sql Server Driver]Communication link failure
I am running Sql 2000 SP 3. Both my pc and the server are running Windows
2000.
If I use a different pc under the same login I am able to connect to the
server so the problem must be on my individual pc. I can also connect to
other Sql servers from the pc that is giving me problems. I have tried
uninstalling and reinstalling Sql and I get the same error message.
Does anyone have any idea as to the cause of this?Update...
I am able to register the server via IP address but not server name. When I
register by IP I get the same message that says:
SQL Server registration failed because of the connection failure displayed
below. Do you wish to Register anyway?
Communication link failure
If I click Yes I can then expand the server and view the databases as
normal. When I register by server name I get the same error message but I
still get the Communication link failure when expanding the server.
Help please!!!

Communication Link Failure

Why would we get a " Communication Link Failure "
I have seen " TimeOut Expired " and General Network Error and can
understand why we get those, but what about the one listed in subject
Any idea ?Hi Hassan,
Did you ever find a solution to your problem? I had that same issue
today. I did some research and I found some FAQ that stating:
" Make sure that your largest column is the last column retuned. Make
sure that you do not have any columns returned after a text or an image
column"
I kind of don't fully understand it, but in my case.. I had some columns
will a NULL value at the end of the table. I moved them and it seemed
to fix my problem. Here's the site that I found:
http://www.15seconds.com/faq/ODBC/692.htm
Marc F.
Hassan wrote:
> Why would we get a " Communication Link Failure "
> I have seen " TimeOut Expired " and General Network Error and can
> understand why we get those, but what about the one listed in subject
> Any idea ?
>

Communication link failure

I am running an SSIS packsge across 2 servers. There at 33 Mil rows being copied over. At 5.6 mil rows I get this

[OLE DB Source [1]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Protocol error in TDS stream". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "TCP Provider: The specified network name is no longer available. ".

[DTS.Pipeline] Error: The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Is there any known cause of this?

Thanks

Looks like a connection problem and that something, somewhere starts to drop packets or even the connection. You might have to enlist the help of the network guys if such people exist where you're at.

Communication link failure

I received the Communication link failure from the Windows 2003 Cluster.
What can I do resolve this error?
Thanks,
Error
SQL Server <SQL Server (OLTP)>: [sqsrvres] CheckQueryProcessorAlive:
sqlexecdirect failed
SQL Server <SQL Server (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01;
native error = 0; message = [Microsoft][ODBC SQL Server Driver]Communication
link failure
Joe,
This could indicate a variety of things. You might want to consider
opening a support incident with PSS. They would take you through a variety
of questions to determine the problem. Such as:
First, have you installed SP3?
If not, are you planning on doing so?
Did this just start happening after working for awhile?
Are you using an alias? Has one been recently added?
Check for DSN's that have recently been added.
Check the SQL error log and confirm SQL is listening on TCP, and is
listening on the port you expected.
Check the Private heartbeat configuration and confirm it is set up properly:
Recommended private "Heartbeat" configuration on a cluster server (258750)
http://support.microsoft.com/default...B;EN-US;258750
Are there any events in the system or application event log?
Are there any 17883's in the SQL error log just prior to the communication
link failure?
Any AV's?
Depending on the answers, there could be a number of potential resolutions.
If you would like to continue troubleshooting this yourself, I would follow
the KB article above, try to see if there are any errors, and see if that
gives any clues as to the problem.
The level of troubleshooting to determine the cause, unfortunately depends
on the cause. Sometimes it's very simple, someone changed the alias.
Sometimes it's pretty complex...you have a thread that AV's, causing
17883's and then SQL hangs.
Given that, it might be more expedient for you to open a case with PSS.
Hope that helps!
Donna Lambert
SQL Server Product Support Services