September 7, 2017 at 3:17 pm
Hoping you can help
Server: Windows Server 2012
SQL: SQL Server 2014 SP2 CU5
We have several ODBC connections on the server connecting to the instance and suddenly they are failing. When I go through the configuration to test - the first test fails with
Attempting connection
[Microsoft][ODBC SQL Server Driver]Login timeout expired
Disconnecting from server
But when I test it again it works fine.
I unchecked Use strong encryption for data and now the tests work fine everytime.
Any help would be appreciated.
Jeff
September 7, 2017 at 5:42 pm
More information
Set turned off encryption of data in transit - still failed
Checked these recent update - nothing seamed to cause this issue
I am trying to figure out what was changed what rights were taken away to cause this issue,
How does the encryption work anyway.
In SQL Log nothing is showing
Windows Event Log nothing is showing
Trying to run the ODBC tracing - No log is generated.
Any feedback is appreciated.
Jeff
September 8, 2017 at 4:08 am
sounds like it could be a TLS issue
Have you disabled TLS1.0 and only using TLS1.2 by any chance
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 8, 2017 at 8:17 am
Thanks for the reply
Yes TLS 1.0 is disabled and TLS 1.2 is enabled - No changes to this
Its crazy because its all our SQL Servers in every environment PRD, DEV, TST, TRN, IVV and it was working Wednesday and Thursday everything went down. We spoke to NetOps and nobody pushed anything.
We are considering updating the SQL Server Driver in the ODBC, but these are hard to fine
The current version of drivers are
ODBC Driver 11 for SQL Server - 2014.120.5546.00
SQL Server - 6.03.9600.17415
SQLK Server Native Client 11.0 2011.110.6518.00
We are looking into a maybe a certificate expired since its everything all at the same time.
Your feed back is appreciated.
Jeff
September 8, 2017 at 8:23 am
jayoub - Friday, September 8, 2017 8:17 AMThanks for the reply
Yes TLS 1.0 is disabled and TLS 1.2 is enabled - No changes to this
Its crazy because its all our SQL Servers in every environment PRD, DEV, TST, TRN, IVV and it was working Wednesday and Thursday everything went down. We spoke to NetOps and nobody pushed anything.
We are considering updating the SQL Server Driver in the ODBC, but these are hard to fine
The current version of drivers are
ODBC Driver 11 for SQL Server - 2014.120.5546.00SQL Server - 6.03.9600.17415
SQLK Server Native Client 11.0 2011.110.6518.00
We are looking into a maybe a certificate expired since its everything all at the same time.
Your feed back is appreciated.
update the odbc drivers to the very latest, had the same issue myself recently
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
September 8, 2017 at 8:24 am
By the way. If i could just uncheck the Use strong encryption It would work fine
Jeff
September 8, 2017 at 8:26 am
I also noticed that if I create an ODBC connection from any other machine, server or workstation it connects fine using the encrpytion
Jeff
September 8, 2017 at 2:11 pm
The problem has gone away.
We are not sure what happened, but suddenly the ODBC connections began working again.
We suspect that someone at a higher level IT department had done something and after our frantic calls un did it. They have not told us what, but I sure would like to know.
We suspect a certificate issue, but cannot be sure
Is there any information about how the ODBC encryption works - some good details about ODBC in general would even help.
Thanks for the feedback today
Jeff
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply