Receiving Timeout/Communication link Failure

Question

Receiving Timeout/Communication link Failure

Guedel, Christopher 0

Hello,

I am receiving an error when our PHP intranet page executes a Stored Procedure through ODBC. The offending SQL Server instance is SQL Server 2017 version 14.0.2052.1. We are running the most up to date GDR update, with the possibility of updating to the CU path of CU 31 14.0.3445.1. Our TEST and DEV environments are running CU 31, and do not have this issue.

Is this a matter of updating our SQL Server version, or is this an ODBC/Network issue?

Message: [Microsoft][ODBC Driver 13 for SQL Server]TCP Provider: Timeout error [258].

SQLState: 08S01

Error Code: 258

Message: [Microsoft][ODBC Driver 13 for SQL Server]Communication link failure

SQLState: 08S01

Error Code: -2147467259

Message: [Microsoft][ODBC Driver 13 for SQL Server]Communication link failure

2 answers

Your answer

Answer 1

Erland Sommarskog 121.4K MVP Volunteer Moderator

For the Communication link failure, I would check the SQL Server log to see if there are stack dumps that coincide with these messages. If there are, there is all reason to apply CU31.

Then again, why would you not apply CU31 and get many bug fixes?

However, while CU31 may solve these problems, they may also be due to situations that do not occur in DEV or TEST because of differences in data and workload. Or network connections. But I think you should start with CU31, to get that out of the equation.

Guedel, Christopher 0 Reputation points

2023-12-19T22:47:36.8333333+00:00

The SQL Server logs is showing: Error 17832 The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.

From the Error coding on Microsoft's learn site, there is a possible fix of increasing the Max Token Size.

The issue is that the SQL Server Logs don't have a corresponding entry for each PHP Error occurrence we are seeing.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-12-19T22:51:19.4533333+00:00

I would say that it more sounds like network component garbling the bytes than an SQL Server issue. I would still recommend CU31, though. I think there is little reason to run with only RTM + GDR fixes.
Guedel, Christopher 0 Reputation points

2023-12-20T14:11:01.4866667+00:00

In looking at the Security Updates after CU31, KB5029376 has 3 components available for download. I see the update named SQLServer2017-KB5029376-x64.exe, but there is also two more available for download named SQLEXPRADV_x64_ENU.exe and SQLEXPR_x64_ENU.exe.

Those two files look to be SQL Server 2017 Express installs. Why would there need to be SQL Server 2017 Express installs for this update and is it needed or can just the update be ran like all other Security Updates?

Thank you
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-12-20T19:55:50.7133333+00:00

You would only use the Express installs, if your instance is Express Edition. But you are right, there has been at least one GDR after CU31, and you are likely to have that security fix installed on your current instance, so quite clearly, you want to keep that fix.

Answer 2

Olaf Helper 47,436

[Microsoft][ODBC Driver 13 for SQL Server]

Also, version 13 is a bit old, you gave the latest version 17 a try

https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16

Guedel, Christopher 0 Reputation points

2023-12-20T14:36:17.03+00:00

We're running some older PHP code that we are working on refactoring and bringing up to 8.0, so I am hesitant to upgrade to the newest ODBC version if it will create more errors and warnings to go through.

Will updating to the newest ODBC driver cause issues with older(7.x, 8.0.28) PHP code and our Stored Procedure calls is my concern prior to updating to the newer version.

Thank you

Share via

Receiving Timeout/Communication link Failure

2 answers

Your answer