March 9, 2023 at 4:52 pm
Hello experts,
I'm trying to help troubleshoot an issue affecting the connections between one of our Linux application servers and one of SQL 2016 servers.
Source OS/Driver:
Red Hat Enterprise Linux 7 (64-bit)
ODBC Driver 11 for SQL Server
Destination OS/SQL:
Windows Server 2016 Standard
Microsoft SQL Server 2016 (SP3-CU1-GDR) (KB5021128) - 13.0.7024.30 (X64)
The reported error is usually this one:
[SQLSTATE=08S01] [Microsoft][ODBC Driver 11 for SQL Server]TCP Provider: Error code 0x274C
The occurrences are generally grouped within a two-hour time frame in the early mornings, but occasionally some are much later, around 7-9 am, and the frequency of the occurrences is increasing, so this has become a bigger problem. Basically, a Perl script's processing gets interrupted, which causes one or more jobs to fail, and the app team reports it in frustration, and so on each time.
My general question is - can anyone point me to a checklist or troubleshooting guide of how to methodically troubleshoot this issue?
I've checked a few things in an ad hoc manner, but I don't think I have really been systematic about trying to find the root cause. I've even seen a comment suggesting running an ODBC trace, but I am not sure whether to run the trace on the source, the destination, or both.
We have also reported it to our networking team to see what they can find, but again I don't know what info I should provide to them to help.
Thanks for any help!
-- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
March 10, 2023 at 11:42 am
I don't have experience with sql on linux
What have you tried?
Found an extensive troubleshooting list on stackoverflow https://stackoverflow.com/questions/64876580/sql-server-odbc-tcp-provider-error-code-0x274c
March 10, 2023 at 4:18 pm
Hi Jo,
Thanks. To be honest, I have not tried much yet, as the connection is not making it to the SQL Server when this issue happens, so nothing is logged in the SQL Server error log. I am checking the event logs as well but so far nothing relevant has shown up.
But I will see what the network team reports about the health of the underlying network.
Also, I'm planning on setting up the ODBC trace on the Windows (SQL) side as well as working with the application team to have them set up an ODBC trace on the Linux side, which I think should be possible if they have ODBC drivers.
I'll report back asap with more info.
Thanks again!
-- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply