TD6.3.10 - connect to sql server produce invalid COM dll error

Discussion forum about all things Team Developer 5.x and 6.x
chrisylt
Canada
Posts: 6
Joined: 29 Aug 2018, 22:12
Location: Vancouver, Canada

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by chrisylt » 30 Aug 2018, 21:22

Hi,

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

[odbcrtr]
enablemultipleconnections=on
FETCHROW=2
REMOTEDBNAME=SSMASTER2016,Driver=SQL Server Native Client 11.0;Server=dga1tdgdev005\SS2016;Database=SDV_MASTER;ANSINPW=YES;QUOTEDID=YES
REMOTEDBNAME=SSMASTER2012,Driver=SQL Server;Server=dga1tdgdev005;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.

Samad Sodul
Mauritius
Posts: 7
Joined: 29 Aug 2018, 15:21
Location: Mauritius

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by Samad Sodul » 31 Aug 2018, 15:29

Hi
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


thanks

s.

chrisylt
Canada
Posts: 6
Joined: 29 Aug 2018, 22:12
Location: Vancouver, Canada

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by chrisylt » 31 Aug 2018, 16:48

Hi,

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)

Chris

a_sivababu
India
Posts: 62
Joined: 10 Mar 2017, 08:46
Location: Chennai,India

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by a_sivababu » 02 Sep 2018, 05:39

Hi
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.

Thanks
Siva A

Samad Sodul
Mauritius
Posts: 7
Joined: 29 Aug 2018, 15:21
Location: Mauritius

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by Samad Sodul » 02 Sep 2018, 06:41

Hi
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.

Thanks

Samad

FRBhote
India
Posts: 1231
Joined: 09 Mar 2017, 05:32
Location: Hyderabad, India

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by FRBhote » 03 Sep 2018, 05:08

Connection is busy with results for another hstmt (when doing an execute in a loop with another SQL Handle)
This is the MARS problem when you use the Native Client. Use the regular Sql Server driver.

QRTL
Austria
Posts: 1
Joined: 04 Sep 2018, 10:35
Location: Austria

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by QRTL » 05 Sep 2018, 04:28

We have also the same problem with the new Driver "ODBC Driver 13 for SQL Server --> "Invalid character value for cast specification"
Reason for the change is the TLS 1.2.

Is there a solution for the problem??

FRBhote
India
Posts: 1231
Joined: 09 Mar 2017, 05:32
Location: Hyderabad, India

TD6.3.10 - connect to sql server produce invalid COM dll error

Post by FRBhote » 05 Sep 2018, 05:51

Had that problem with 7, but it got solved with 7.1.

Runs ok in Sqltalk & SSMS?

Raise a ticket?

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests