Microsoft OLE DB Provider for SQL Server__Login failed for user '(null)'. I have been using my workstation on a Windows 2000 SQL Server network for several weeks without any issues. I am using Activant Prophet 21 accounting software along with MS Office 2010 Professional on a Windows 7 Ultimate platform. HiThe readme file for SQL Server 2005 says: 4.10.1 Obtaining the Microsoft OLE DB Provider for DB2. Lsi megaraid sas controller drivers.
Our client recently upgraded from TLS 1.0 to TLS 1.2 and after this our software cannot connect with SQL server. It uses OLE DB provider for connecting to SQL server.Below is the error which is returned from SQL server-
[DBNETLIB][ConnectionOpen SECDoClientHandshake()]SSL Security errorSQL State: 08001SQL Error Number: 18
Could not find any useful information related to whether Microsoft OLE DB Provider for SQL Server support TLS 1.2 or not.
One of the links I found seems to suggest that it is not supported.https://forums.iis.net/t/1233674.aspx?connecing+SQL+server+DB+issue+after+installingTLS1+2+in+SQL+srver+with+classic+asp+application+
Hence, wanted to check on stackoverflow in case anyone has any information on this.
Amit RastogiAmit Rastogi
33411 gold badge33 silver badges1616 bronze badges
3 Answers
The SQLOLEDB provider and the SQL Server ODBC driver that ship with Windows are legacy components provided only for backwards compatibility. These have been deprecated since SQL 2005.
According to this blog post by the MSSQL Tiger Team:
SQLOLEDB will not receive support for TLS 1.2. You will need to switch your driver to one of the supported drivers listed in https://support.microsoft.com/en-us/kb/3135244
You should be able to install SQL Server Native Client 2012 and use that OLE DB provider with only a connection string change (change
Provider=SQLOLEDB to Provider=SQLNCLI11 ). Of course, once should test to avoid surprises. For example, I recall someone experiencing behavior differences with the SQL Server Native Client provider and ADO classic when server API cursors were used, although the commonly used firehose cursors were fine.
The new OLE DB driver, MSOLEDBSQL, has been released. This new driver includes the support for the latest TLS 1.2 standards and is backwards compatible with SQL Server Native Client 11 (SQLNCLI11). See the Microsoft SQLNCLi team blog announcement.
Dan GuzmanDan Guzman
25.8k33 gold badges1919 silver badges4343 bronze badges
Free ios games download. This may not be a solution for you, since it's a future fix your client may not be able to wait for, but apparently Microsoft is undeprecating the OLEDB Driver, with a new release supporting TLS 1.2 out Q1 2018: https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-release-of-ole-db-driver-for-sql-server/
The new Microsoft OLE DB Driver for SQL Server, or msoledbsql, will also introduce multi-subnet failover capabilities in this first upcoming release, and keeps up with latest TLS 1.2 standards.
![]()
Also, this first upcoming release will be a stand-alone install package that is out-of-band with SQL Server lifecycle. This also means the driver will not be packaged in the SNAC library, nor coupled with any other driver.
Dan Guzman
25.8k33 gold badges1919 silver badges4343 bronze badges
SeanGSeanG
Following changes on my end fixed the issue after TLS1.2 upgrade on Azure cloud -
Microsoft Ole Db Provider For Odbc Drivers Download Windows 10
4,43266 gold badges1818 silver badges3030 bronze badges
Manish GohilManish Gohil
Microsoft Ole Db Provider For Sql Server Download FreeNot the answer you're looking for? Browse other questions tagged sql-serveroledbtls1.2 or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |