November 23, 2023 at 4:05 am
We have SQL server 2012 installed and running successfully.
Getting the error message 10054 client unable to establish the connection. Matched the TLS protocol. Is there any windows query to check which Cipher suits will be using by server & client.
Thanks,
Ramana
November 23, 2023 at 11:32 am
No tech from this decade then?
All jokes aside,
XP out of support
2012 out of support
SQL Native client (all versions) out of support
You shouldn't be running stuff on these platforms any more. Seriously you need to upgrade your tech stack.
But 10054 has a number of causes, could be TLS, could be Kerberos, could be anything
Network Interruptions: Check for network interruptions or instability. It could be due to a temporary network problem, such as a timeout or network congestion.
Firewall or Antivirus Settings: Ensure that your firewall or antivirus software isn't blocking the SQL connection. Sometimes, security software can interfere with network connections.
Server/Client Configuration: Verify the configuration settings on both the SQL Server and the client-side. Ensure they match and are correctly configured.
SQL Server Logs: Check the SQL Server logs for any additional error information or warnings related to this issue.
Driver or Provider Issues: If you're using ODBC, JDBC, or other drivers to connect to the SQL Server, ensure they are up-to-date. Outdated drivers can sometimes cause connectivity problems.
Network Hardware: Check network hardware, such as routers, switches, or cables for potential issues. A faulty network device could cause intermittent connection problems.
Client Application: If the error occurs within a specific application, try connecting from a different application or method to isolate if the issue is application-specific.
Restart Services: Sometimes, restarting the SQL Server service or related services can resolve temporary network-related issues.
But you either need a different driver something like ODBC or JDBC or get on a supported set of technologies.
November 23, 2023 at 11:34 am
No tech from this decade then?
All jokes aside,
XP out of support
2012 out of support
SQL Native client (all versions) out of support
You shouldn't be running stuff on these platforms any more. Seriously you need to upgrade your tech stack.
But 10054 has a number of causes, could be TLS, could be Kerberos, could be anything
Network Interruptions: Check for network interruptions or instability. It could be due to a temporary network problem, such as a timeout or network congestion.
Firewall or Antivirus Settings: Ensure that your firewall or antivirus software isn't blocking the SQL connection. Sometimes, security software can interfere with network connections.
Server/Client Configuration: Verify the configuration settings on both the SQL Server and the client-side. Ensure they match and are correctly configured.
SQL Server Logs: Check the SQL Server logs for any additional error information or warnings related to this issue.
Driver or Provider Issues: If you're using ODBC, JDBC, or other drivers to connect to the SQL Server, ensure they are up-to-date. Outdated drivers can sometimes cause connectivity problems.
Network Hardware: Check network hardware, such as routers, switches, or cables for potential issues. A faulty network device could cause intermittent connection problems.
Client Application: If the error occurs within a specific application, try connecting from a different application or method to isolate if the issue is application-specific.
Restart Services: Sometimes, restarting the SQL Server service or related services can resolve temporary network-related issues.
But you either need a different driver something like ODBC or JDBC or get on a supported set of technologies.
November 24, 2023 at 1:07 pm
Due to vendor Application we have to stick the os old version on the client. We can’t use the latest version of SQL server but support sql 2008 or 2012.
We have disabled the TLS.
November 24, 2023 at 2:25 pm
Given the whole technology stack is 15 years + out of date, and if it works with SQL 2008, just run it on 2008.
Trade 1 unsupported platform for another.
No point trying to make it work now.
But get on to the vendor and get them to give you an updated app which works on some form of tech which is from the last couple years
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply