SSL Error in Big Query using Simba ODBC Driver C# - ssl

I am using Simba ODBC driver (32-bit) to query data from Google Big Query using C#. I keep getting the below error one or two times per week. Please help as I am not sure how to resolve this error.
ERROR [HY000] [Simba][DriverSupport] (1160) Cannot enable SSL for the
connection when connecting to a server that has not enabled SSL. If
the server has SSL enabled, please check if it has been configured to
use a SSL protocol version that is lower than what is allowed for the
connection. The minimum SSL protocol version allowed for the
connection is: TLS 1.1.

Related

Connecting SQL Server To Cognos Free Trial Version

I had subscribed for free trial for IBM Cognos. In that I have to connect my SQL server with it. I had tried all alternatives but none is working. According to the error, I had even given access of firewall through my system with port defined, also in sql server configuration manager. But still facing the same error when Testing the connection through ibm cognos.By default, we can only connect through jdbc.
Error
Connection In cognos
SQL Server configuration manager
Port Setting Inbound Firewall
The MSSQL database you are connecting to would not be local to the on demand server, so a host of localhost is likely not correct.
If the MSSQL is not publicly accessible you will need to use a secure gateway connection. https://www.ibm.com/docs/kk/cognos-analytics/11.1.0?topic=demand-secure-gateway-only
Additionally, public or private you will also need to add the following to the JDBC connection URL TrustServerCertificate=true

I have installed Lince Bi on Windows machine but on connecting SQL server it is showing SSL error

I have installed Lince Bi on Windows machine but on connecting SQL server it is showing SSL error.
"com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "No trusted certificate found". ClientConnectionId:92c4c4cd-5088-45d0-97c6-363303c25af1
"
I already added trust certificate
If the driver keeps failing with the encryption error, make sure to provide the "Encrypt=false" parameter to the data source.
You need to provide the apropriate Microsoft JDBC driver in order to LinceBI work correctly as well.
You can download it from Microsoft: Download Microsoft JDBC Driver for SQL Server
I use mssql-jdbc-10.2.1.jre8.jar because I'm using Java JDK 8.
The driver must be put inside the lincebi_web\tomcat\lib directory.
Best Regards!

SQL Server ODBC Connect to Database Fails With "SSL Security Error"

I have been digging for answers for this issue and have not been able to solve it. I believe it is a TLS issue but nothing I've tried fixes it. Setup ...
The reporting application server trying to connect to the database server via ODBC SQL Server is using the SQLSRV32.DLL version 6. (I know the driver is old and updating would probably fix the issue but that is not so easy to do). I have confirmed on both hosts that TLS 1.0 is not enabled. I did this by checking the registry under "SCHANNEL->Protocols" and using "Internet Options -> Advanced Tab". Both only have TLS 1.1 and TLS 1.2 checked. The error is "Error 772; Connection Failed; SSL Security Error". I found a host with an updated ODBC driver (v10) and it can connect to the database.
I have another DB and reporting server with what appears to be identical configurations, using the same old SQL driver, but they are not having the issue. Trying to connect from this reporting server to the other database fails too.
I believe this is an issue with the database server, possibly SQL Server, but am stuck on what to look for.
Any guidance on what else to look at would be appreciated.

DAL01013: Cannot connect to server

I'm trying to connect to DB2 db but getting the error:
DAL01013. Cannot create connection to server 'Unknown server' due to the following: [jcc][t4][2034][11148][3.69.24] Execution failed due to a distribution protocol error that caused deallocation of the conversation.
A DRDA Data Stream Syntax Error was detected. Reason: 0x3. ERRORCODE=-4499, SQLSTATE=58009
Assume it's something with my system. I cannot connect neither via DataStudio nor via QMF. Other users from other system can. I use same jdbc drivers. My system is Windows 7.
Is there anything else I need to adjust on my system?
Personal repository needs to be created first:
https://developer.ibm.com/answers/questions/470013/error-when-trying-to-connect-to-db2-vis-qmf/
Generally you get the reason 0x3 from error -4499 out of the IBM JDBC driver when you are connecting to a SSL port, but you have not specified sslConnection=true on your JDBC connection string. You can also get the error if your database name is incorrect (i.e. does not exist on the server), or your JDBC dirver is too old (DB2 JDBC Driver Versions and Downloads Download Fix Packs by version for IBM Data Server Client Packages)
If connecting to Db2 on Cloud, Db2 Warehouse or Db2 Warehouse on Cloud, all you should need is the sslConnection=true as the CA certificate used in these products is part of the Db2 driver package (for recent drivers anyway)
If connecting to Db2 on premise, you can specify your certificate location via the JDBC properties sslCertLocation or sslTrustStoreLocation and sslTrustStorePassword
Common IBM Data Server Driver for JDBC and SQLJ properties for all supported database products
sslCertLocation
Specifies that an application can configure the location of a trusted certificate file. For applications that have the database server certificate, sslCertLocation is the only property that is needed to be configured to instruct IBM Data Server Driver for JDBC and SQLJ to trust the certificate for SSL connections.
This property removes the need to import the certificate into a Java truststore database and related driver configurations.
Error codes issued by the IBM Data Server Driver for JDBC and SQLJ
error codes in the ranges -4200 to -4299, and -4450 to -4499 are reserved for the IBM® Data Server Driver for JDBC and SQLJ.

Connection to SQL database failed because of an error in initializing provider

I am trying to connect to an internal SQL database which allows TLS 1.2 protocol only.
I am able to log-in to the database using the SQL Server Management studio.
I'd like to connect to that same database using Excel 2013 (for a more graphic report). I have read a lot on Excel having problems with TLS1.2 and the use of ODBC Driver instead since that is the only one which supports tls 1.2.
Sadly when entering the credentials and testing the connection we receive the following error:
TEST CONNECTION FAILED BECAUSE OF AN ERROR ININITIALIZING PROVIDER. UNSPECIFIED ERROR
Does anybody have experience with using Excel to connect to SQL Server using TLS1.2? Am I doing something wrong? I'm using the Data link: Microsoft OLE DB Provider for ODBC drivers. The normal SQL way of adding things doesn't work either but I believe that's because TLS1.2 isn't supported there.
If I recall correctly, Management Studio will connect on port 1433 by default and use the TDS protocol and really have nothing to do with TLS. So it is not surprising that it works in SSMS.
From https://blogs.msdn.microsoft.com/sql_pfe_blog/2017/09/27/microsoft-excel-tls-sql-server-important-considerations/
For all NEW workbooks, do not use that menu option. Instead use the
"From Data Connection Wizard" and select a compliant driver from the
list. A requirement is that you have the SQL Native Client (2008 or
2012) or ODBC drivers with appropriate patches per TLS 1.2 support for
Microsoft SQL Server below.
So it seems like just using ODBC will not work unless ODBC on your machine has been patched to handle TLS 1.2.
I believe the ODBC update you need is below.
https://www.microsoft.com/en-us/download/details.aspx?id=36434&751be11f-ede8-5a0c-058c-2ee190a24fa6=True