I am testing TD 6.3.10. When trying to create a connection to SQL Server in Sql Talk. An error '09267 GCI IDL Invalid COM DLL' is produced. This is the setting in sql.ini
REMOTEDBNAME=SSMASTER2016,Driver=SQL Server Native Client 11.0;Server=dga1tdgdev005\SS2016;Database=SDV_MASTER;ANSINPW=YES;QUOTEDID=YES
neither ssmaster2012 nor ssmaster2016 works
same setting (SSMASTER2012) works in TD 6.0
any help will be much appreciated.
I use Microsoft SQL Server ODBC Driver Version 10.00.17134 (SQLSRV32.DLL) and it runs well for several years.
I tried with SQL Native Client but never succeed ( as It always give me Microsoft][SQL Server Native Client 11.0]Invalid character value for cast specification ) and sometimes
Connection is busy with results for another hstmt.
Try to use the above to check and please provide me the configuration settings to make ODBC works with SQL Native client
We use SQL Server ODBC driver (Version 10.00.15063.00) in our production environment and it works well. However, we discovered this driver doesn't work if you are connecting to SQL Server 2016 with TLS 1.0 disabled. That is why we start investigating the SQL Server Native Client. FYI, Unify 7.1 works with SQL Server Native Client. However, we notice performance issue in certain area (See my other post in the 7.* forum)
Can you please try to use the ODBC Driver 13.1 if you have not tried and check whether this is working with TLS disabled.
https://www.microsoft.com/en-us/downloa ... x?id=53339
I have invested good amount of time to test SQL Server Native Client, OLEDB and ODBC Drivers but the best one is on ODBC driver. I have also explored the internet and Microsoft is betting on ODBC driver to deploy in Cloud or On Premises across the OS platform than SQL Server Native Client or OLEDB. This is my understanding and may not be correct too.
I tried ODBC Driver 13 for SQL Server [MSODBCSQL13.DLL] ( but It always give me Microsoft][SQL Server Native Client 11.0]Invalid character value for cast specification ) on date field and sometimes
Connection is busy with results for another hstmt (when doing an execute in a loop with another SQL Handle)
However connection using SQLSRV32.DLL r run perfectly well with same source codes. My applications run well for many years on all SQLSERVER database (2000-2017) with ODBC connection SQLSRV32.dll
I am now using TD6.3.9 with same problem. I will be very grateful if someone who find me a solution.
This is the MARS problem when you use the Native Client. Use the regular Sql Server driver.Connection is busy with results for another hstmt (when doing an execute in a loop with another SQL Handle)
Reason for the change is the TLS 1.2.
Is there a solution for the problem??
Runs ok in Sqltalk & SSMS?
Raise a ticket?
Who is online
Users browsing this forum: [Ccbot] and 0 guests