How To Install Odbc Driver 11 For Sql Server

000177133 kA74Q0000004XXtSAM

Article

Title	Connection to MS SQL Server 2014 using ODBC Driver 11 for SQL Server fails with errors.

URL Name	OE-Dataserver-MS-SQL-Server-11-5-1-ODBC-error-connect-to-SQL-2014-Server

Environment	Product: OpenEdge Version: 11.5.x, 11.6.x OS: Windows Other: Microsoft SQL Server 2014, ODBC Driver 11 for SQL Server (version 2014.120.4219.00)

Question/Problem Description	Connection to MS SQL Server 2014 fails with ODBC Driver 11 for SQL Server. Attempt to retrieve the MS SQL database schema definition from the OpenEdge DataServer using the ODBC driver 11 for SQL fails with errors. The migration of the sample sports2000 OpenEdge database to MS Sql Server 2014 via the pro-to-mss utility also fails with errors. Is "ODBC Driver 11 for SQL Server" driver certified with OE DataServer 11.5 and 11.6?

Question/Problem Description

Connection to MS SQL Server 2014 fails with ODBC Driver 11 for SQL Server.
Attempt to retrieve the MS SQL database schema definition from the OpenEdge DataServer using the ODBC driver 11 for SQL fails with errors.
The migration of the sample sports2000 OpenEdge database to MS Sql Server 2014 via the pro-to-mss utility also fails with errors.
Is "ODBC Driver 11 for SQL Server" driver certified with OE DataServer 11.5 and 11.6?

Clarifying Information	Connecting to a MS SQL Server 2014 with the OE 11.5.1 DatasServer for MS SQL Server . Using the "ODBC driver 11 for SQL" that is shipped by default with MS SQL server 2014. Starting with OpenEdge 11.3, the DataServer is certified against MS SQL Server 2014. "SQL Native Client 11" and "ODBC driver 11 for SQL server" are two distinct ODBC drivers. As a matter of fact their dll names are different. (MSODBCSQL11.DLL vs SQLNCLI11.DLL):

Clarifying Information

Connecting to a MS SQL Server 2014 with the OE 11.5.1 DatasServer for MS SQL Server .
Using the "ODBC driver 11 for SQL" that is shipped by default with MS SQL server 2014.
Starting with OpenEdge 11.3, the DataServer is certified against MS SQL Server 2014.

"SQL Native Client 11" and "ODBC driver 11 for SQL server" are two distinct ODBC drivers. As a matter of fact their dll names are different. (MSODBCSQL11.DLL vs SQLNCLI11.DLL):

User-added image

Error Message	•S1090: [Microsoft][ODBC Driver Manager] Invalid string or buffer length •Wrong procedure handle for SEND-SQL-STATEMENT, or SEND-SQL-STATEMENT is not active. (2099) •S1010: [Microsoft][ODBC Driver Manager] Function sequence error

Cause	The "ODBC driver 11 for SQL server" is currently not certified against DataServer 11.5 and 11.6. According to the OpenEdge product availability guide, the following ODBC drivers are certified with MS SQL Server 2014: SQL Native Client 11 SQL Native Client 10 SQL Native Client 9 SQL Server Data Direct ODBC 7.1 driver (OpenEdge 11.5 Legacy Wire Protocol Driver for MS SQL Server)

Resolution	Use one of the supported drivers to connect to the MS SQL Server 2014.

Last Modified Date	11/20/2020 7:21 AM

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation ("Progress"). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.