blocks|key|1137658|text|可能已经安装了ODBC+11.0早期版本。在这种情况下，连接字符串应该是Driver={ODBC+Driver+11+for+SQL+Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1137659|并检查是否启用了TLS+1.2|1137660|entityMap^0|7|9|10|2X|0|8|7|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

There might be chances that <code>ODBC 11.0</code> earlier version is been installed. In this case the connection string should be 
<code>Driver={ODBC Driver 11 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;</code>

And also check <code>TLS 1.2</code> is enabled

blocks|key|1137685|text|在Windows+2016上禁用TLS1.0和1.1之后，我们能够以以下方式使我们的ASP经典脚本数据库连接再次工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1137686|下载并安装Microsoft+SQL+Server驱动程序+(MSOLEDBSQL)|ordered-list-item|offset|length|1137687|在ASP.NET经典脚本的所有连接字符串中将Provider=SQLOLEDB;替换为Provider=MSOLEDBSQL;|style|CODE|1137688|完成了！(不需要重新启动)|1137689|注意:以前的Microsoft+OLE+DB+provider+for+SQL+Server+(SQLOLEDB)和SQL+Server本机客户端OLE+DB提供程序(SQLNCLI)仍然不推荐使用，因此不建议将其用于新的开发工作。(来源)|1137690|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver15|1|https://learn.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15^0|0|5|O|0|0|M|I|17|K|0|0|39|2|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@$E|10|F|11|1|12]]|A|$]]|$1|G|3|H|5|D|7|13|8|@$E|14|F|15|I|J]|$E|16|F|17|I|J]]|9|@]|A|$]]|$1|K|3|L|5|D|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|O|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

After disabling TLS 1.0 and 1.1 on Windows Server 2016 we were able to get our ASP Classic scripts database connections working again in the following way:
<ol>
<li>Download and install <a href="https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver15" rel="nofollow noreferrer">Microsoft OLE DB Driver for SQL Server</a> (MSOLEDBSQL)</li>
<li>Replace <code>Provider=SQLOLEDB;</code> with <code>Provider=MSOLEDBSQL;</code> in all connection strings for the ASP Classic scripts</li>
<li>Done! (no restart needed)</li>
</ol>
Note: The previous (same name but different abbreviation) Microsoft OLE DB Provider for SQL Server (SQLOLEDB) and SQL Server Native Client OLE DB provider (SQLNCLI) remains deprecated and it is not recommended to use either for new development work. (<a href="https://learn.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-server-ver15" rel="nofollow noreferrer">source</a>)

blocks|key|599341|text|我不得不做几件事。该服务器是Windows2016Standard测试，我将一个.txt文件更改为.UDL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|599342|在2016年框上安装了Server本机客户端10.0|599343|在这里找到它：https://www.microsoft.com/en-us/download/details.aspx?id=57606|offset|length|599344|最后，在sql+server框上，我必须安装修补程序KB4057113以启用TLS1.2。|599345|注意:当通过打开.UDL文件测试连接时，不要忘记将提供程序更改为SQLServerNativeClient10.0|599346|entityMap|0|LINK|mutability|MUTABLE|url|https://www.microsoft.com/en-us/download/details.aspx?id=57606^0|0|0|7|1Q|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I had to do several things. The server was Windows 2016 Standard testing with a .txt file I changed to .UDL. This server was trying to connect to our Sql Server 2008 R2 SP3 

On the 2016 box I installed SQL Server Native client 10.0

Get that here : <a href="https://www.microsoft.com/en-us/download/details.aspx?id=57606" rel="nofollow noreferrer">https://www.microsoft.com/en-us/download/details.aspx?id=57606</a>

Finally on the sql server box I had to install patch KB4057113 to enable TLS1.2

Note when testing the connection by opening the .UDL file don't forget to change the provider to SQL Server Native Client 10.0

blocks|key|1137766|text|和Jonas+Appelgran的回答相似，但是为了解决我们的问题，做了一些小小的改动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1137767|下载并安装Microsoft+SQL+Server驱动程序+(MSOLEDBSQL)|ordered-list-item|offset|length|1137768|在ASP.NET经典脚本的所有连接字符串中将Provider=SQLOLEDB;替换为Provider=MSOLEDBSQL19;+(注意需要驱动程序的版本)|style|BOLD|1137769|此时，仍有以下错误：|1137770|SSL提供程序:证书链是由不受信任的权威机构颁发的。|blockquote|1137771|经过一些研究后，我发现我还需要信任服务器证书，或者在连接字符串中将加密设置为false：|1137772|信任服务器Certificate=True;和/或将加密用于Data=False;|1137773|需要根据您的情况更新这些，但是它只是一个内部intranet应用程序，所以这两个选项都可以。(否则，您需要创建和安装自签名证书或来自组织CA的证书。)|1137774|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16^0|0|5|O|0|0|M|I|17|M|0|0|0|0|0|M|P|G|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@$E|15|F|16|1|17]]|A|$]]|$1|G|3|H|5|D|7|18|8|@$E|19|F|1A|I|J]|$E|1B|F|1C|I|J]]|9|@]|A|$]]|$1|K|3|L|5|D|7|1D|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@$E|1H|F|1I|I|J]|$E|1J|F|1K|I|J]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1L|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

Similiar to Jonas Appelgran's answer, but some slight changes to solve our issue.
<ol>
<li>Download and install install <a href="https://learn.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16" rel="nofollow noreferrer">Microsoft OLE DB Driver for SQL Server</a> (MSOLEDBSQL)</li>
<li>Replace Provider=SQLOLEDB; with Provider=MSOLEDBSQL19; in all connection strings for the ASP Classic scripts (note the version of the driver was needed)</li>
<li>At this point, was still getting the following error:</li>
</ol>
<blockquote>
SSL Provider: The certificate chain was issued by an authority that is
not trusted.
</blockquote>
After some research, I found that I also needed to either trust the server certificate or set the encryption to false in the connection string:
Trust Server Certificate=True;
and/or
Use Encryption for Data=False;
Need to update these depending on your situation but it was an internal intranet application only for us so either option was fine. (Otherwise you would need to create and install either a self-signed certificate or one from your organization's CA.)

blocks|key|599299|text|打开Regedit+(Wind%2BR+>+regedit)|type|ordered-list-item|depth|inlineStyleRanges|entityRanges|data|599300|定位HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib|599301|创建一个新单词值并将其命名为“证书”，将值设置为："Certificate=0“|599302|还修改默认的REG_SZ并将值设置为"Certificate=0“|599303|重新启动MSSQL服务|599304|希望这对我有帮助。|unstyled|599305|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|S|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|T|8|@]|9|@]|A|$]]|$1|M|3|-4|5|L|7|U|8|@]|9|@]|A|$]]]|N|$]]

<ol>
<li>Open Regedit (Wind+R > regedit)</li>
<li>Locate HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetLib</li>
<li>Create a new word value and name it "Certificate" set the value to this: "Certificate=0"</li>
<li>Also modify the default REG_SZ and set the value to "Certificate=0"</li>
<li>Restart the MSSQL service</li>
</ol>

Hope this helps since worked for me.

My server is windows 2008 server r2.
I found the following error on my server after disable tls 1.0 and SSLv3.

<blockquote>
 [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security
 error.
</blockquote>

Currently, only TLS 1.2 is enabled on my server, and at the client side the TLS 1.2 is set on

Is it posible if [DBNETLIB] is running on TLS 1.2?

[DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我的服务器是Windows2008Server r2。禁用TLS1.0和SSLv3后，我在服务器上发现了以下错误。DBNETLIBSSL安全错误。目前，我的服务器上只启用了TLS 1.2，在客户端设置了TLS 1.2如果DBNETLIB运行在TLS 1.2上，是否可行？

问[DBNETLIB][ConnectionOpen (SECCreateCredentials())]SSL安全错误
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问[DBNETLIB][ConnectionOpen (SECCreateCredentials())]SSL安全错误EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问[DBNETLIB][ConnectionOpen (SECCreateCredentials())]SSL安全错误
EN