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