freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
[freetds] Win64 ODBC driver Linked Server for MSSQL 2012
- From: John Kendall <john AT capps.com>
- To: FreeTDS Group <freetds AT lists.ibiblio.org>
- Subject: [freetds] Win64 ODBC driver Linked Server for MSSQL 2012
- Date: Wed, 9 May 2018 03:43:02 +0000
I have MS SQL Server 2012 (named CASTOR) running on Windows Server 2012 R2.
I want to link some servers to it using the FreeTDS ODBC driver.
I've had success with 3 different licensed ($) ODBC drivers, so I know I'm
doing the setup right.
The FreeTDS ODBC driver almost works. Here's an example select on a linked
DSN (named PRODFTDS) created using the FreeTDS ODBC driver:
select * from PRODFTDS...Movetype
Msg 7399, Level 16, State 1
Server 'CASTOR', Line 1
The OLE DB provider "MSDASQL" for linked server "PRODFTDS" reported an
error. The provider reported an unexpected catastrophic failure.
Msg 7330, Level 16, State 2
Server 'CASTOR', Line 1
Cannot fetch a row from OLE DB provider "MSDASQL" for linked server
"PRODFTDS".
movetype move_desc move_revenue
-------- -------------------- ------------
The table Movetype has 3 columns and their names are correctly returned, but
that's all that is returned.
I installed Win32OpenSSL 1.1.0h. I've used various versions of the ODBC
driver from the AppVeyor site, Ramiro's 0.95 branch, and one I compiled
myself with mingw. They all do the same thing.
Can anyone verify that they have had success with the FreeTDS Win64 ODBC
driver for a MSSQL Linked Server? Did I miss an important step? inconv maybe?
The SQL Server logs show a stack dump that reports an access violation. Some
of it is shown below. I can show more if it would be helpful. I'm not sure
how to do a TDSDUMP with ODBC on Windows...
Thanks,
John
SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 05/08/18 20:15:26 spid 64
*
*
* Exception Address = 000000006F7840B5 Module(tdsodbc+00000000000040B5)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 0000000000000090
* Input Buffer 70 bytes -
* select * from PRODFTDS...Movetype
*
*
...
-
[freetds] Win64 ODBC driver Linked Server for MSSQL 2012,
John Kendall, 05/08/2018
- Re: [freetds] Win64 ODBC driver Linked Server for MSSQL 2012, Frediano Ziglio, 05/09/2018
Archive powered by MHonArc 2.6.24.