SQL服务器Azure与.NET连接握手异常 4.5
[英]Handshake exception occurring when connecting to SQL Server Azure with .NET 4.5
问题描述
So I opened up some code that hasn't been touched in about 2 months.
所以我打开了一些大约 2 个月没有被触及的代码。
Last time I opened the application all unit tests passed.上次我打开应用程序时，所有单元测试都通过了。 Now with no code changes all my data unit tests fail with the following error:现在没有代码更改，我的所有数据单元测试都失败并出现以下错误：
Initialization method PerTrac.Pictor.Data.Test.RequestLogRepositoryShould.CreateLog threw exception.
I realize there is an existing question similar to this, but those solutions had no effect what so ever on my situation.我意识到存在与此类似的现有问题，但这些解决方案对我的情况没有任何影响。
Has anyone experienced this error with entity framework and SQL Azure specifically?有没有人在实体框架和 SQL Azure 中遇到过这个错误？
I should note that I can connect from SSMS with no issue using them same credentials.我应该注意，我可以使用相同的凭据毫无问题地从 SSMS 进行连接。 I don't have Force Encryption set on disabled protocols and I have reset my local IIS several times.我没有在禁用的协议上设置强制加密，我已经多次重置本地 IIS。
11 个解决方案
解决方案1
18 已采纳 2013-01-17 18:02:14
Most likely you have some application installed on your computer that is using deprecated network protocols to intercept network traffic. 您很可能在计算机上安装了一些使用不推荐的网络协议拦截网络流量的应用程序。 The correct solution is hopefully to disable or uninstall those applications. 希望正确的解决方案是禁用或卸载这些应用程序。
Run the command line command netsh WinSock Show Catalog >> winsock.txt and then notepad winsock.txt to open the file. 运行命令行命令netsh WinSock Show Catalog >> winsock.txt然后记事本winsock.txt打开文件。
Look at every Winsock Catalog Provider Entry returned. 查看返回的每个Winsock目录提供程序条目 。 If the Service Flags value has the 0x20000 bit set then the provider uses IFS handles and will work fine. 如果Service Flags值设置为0x20000位，则提供程序使用IFS句柄并且可以正常工作。 If the “Service Flags” 0x20000 bit is clear (not set), then it is a non-IFS BSP or LSP and could be an issue. 如果“服务标志”0x20000位清零（未设置），则它是非IFS BSP或LSP，可能是个问题。 Try disabling this application and let us know if it then worked. 尝试禁用此应用程序，然后告诉我们它是否有效。
Ignore the “Name Space Provider Entry” when you are looking at the text file results. 在查看文本文件结果时忽略“名称空间提供者条目”。 They aren't the problem. 他们不是问题。
Below is a sample of what my clean system looks like for the output of the netsh WinSock Show Catalog file. 下面是我的清洁系统对netsh WinSock Show Catalog文件的输出的示例。
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Service Flags: 0x20066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [TCP/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1004
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 1
Protocol: 6
Service Flags: 0x20066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [UDP/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1005
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 2
Protocol: 17
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: MSAFD Tcpip [RAW/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1006
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 3
Protocol: 0
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCPv6 Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1007
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 1
Protocol: 6
Service Flags: 0x22066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP TCP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1008
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Service Flags: 0x22066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDPv6 Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1009
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 2
Protocol: 17
Service Flags: 0x22609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider
Description: RSVP UDP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1010
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Service Flags: 0x22609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [TCP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1001
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Service Flags: 0x20066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [UDP/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1002
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [RAW/IP]
Provider ID: {E70F1AA0-AB8B-11CF-8CA3-00805F48A192}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1003
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 3
Protocol: 0
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [TCP/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1004
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 1
Protocol: 6
Service Flags: 0x20066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [UDP/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1005
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 2
Protocol: 17
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: MSAFD Tcpip [RAW/IPv6]
Provider ID: {F9EAB0C0-26D4-11D0-BBBF-00AA006C34E4}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1006
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 3
Protocol: 0
Service Flags: 0x20609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: RSVP TCPv6 Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1007
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 1
Protocol: 6
Service Flags: 0x22066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: RSVP TCP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1008
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 1
Protocol: 6
Service Flags: 0x22066
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: RSVP UDPv6 Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1009
Version: 2
Address Family: 23
Max Address Length: 28
Min Address Length: 28
Socket Type: 2
Protocol: 17
Service Flags: 0x22609
Protocol Chain Length: 1
Winsock Catalog Provider Entry
------------------------------------------------------
Entry Type: Base Service Provider (32)
Description: RSVP UDP Service Provider
Provider ID: {9D60A9E0-337A-11D0-BD88-0000C082E69A}
Provider Path: %SystemRoot%\system32\mswsock.dll
Catalog Entry ID: 1010
Version: 2
Address Family: 2
Max Address Length: 16
Min Address Length: 16
Socket Type: 2
Protocol: 17
Service Flags: 0x22609
Protocol Chain Length: 1
Name Space Provider Entry
------------------------------------------------------
Description: Network Location Awareness Legacy (NLAv1) Namespace
Provider ID: {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: E-mail Naming Shim Provider
Provider ID: {964ACBA2-B2BC-40EB-8C6A-A6DB40161CAE}
Name Space: 37
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: PNRP Cloud Namespace Provider
Provider ID: {03FE89CE-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 39
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: PNRP Name Namespace Provider
Provider ID: {03FE89CD-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 38
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: Tcpip
Provider ID: {22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: NTDS
Provider ID: {3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0
Name Space Provider Entry
------------------------------------------------------
Description: WindowsLive NSP
Provider ID: {4177DDE9-6028-479E-B7B7-03591A63FF3A}
Name Space: 12
Active: 1
Version: 1
Name Space Provider Entry
------------------------------------------------------
Description: WindowsLive Local NSP
Provider ID: {229F2A2C-5F18-4A06-8F89-3A372170624D}
Name Space: 19
Active: 1
Version: 1
Name Space Provider Entry (32)
------------------------------------------------------
Description: Network Location Awareness Legacy (NLAv1) Namespace
Provider ID: {6642243A-3BA8-4AA6-BAA5-2E0BD71FDD83}
Name Space: 15
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: E-mail Naming Shim Provider
Provider ID: {964ACBA2-B2BC-40EB-8C6A-A6DB40161CAE}
Name Space: 37
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: PNRP Cloud Namespace Provider
Provider ID: {03FE89CE-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 39
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: PNRP Name Namespace Provider
Provider ID: {03FE89CD-766D-4976-B9C1-BB9BC42C7B4D}
Name Space: 38
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: Tcpip
Provider ID: {22059D40-7E9E-11CF-AE5A-00AA00A7112B}
Name Space: 12
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: NTDS
Provider ID: {3B2637EE-E580-11CF-A555-00C04FD8D4AC}
Name Space: 32
Active: 1
Version: 0
Name Space Provider Entry (32)
------------------------------------------------------
Description: WindowsLive NSP
Provider ID: {4177DDE9-6028-479E-B7B7-03591A63FF3A}
Name Space: 12
Active: 1
Version: 1
Name Space Provider Entry (32)
------------------------------------------------------
Description: WindowsLive Local NSP
Provider ID: {229F2A2C-5F18-4A06-8F89-3A372170624D}
Name Space: 19
Active: 1
Version: 1
解决方案2
5 2012-08-24 01:28:40
The key to understand the problem here is the provider and in your case it is "SSL Provider" and the main problem is that connection time out. 解决问题的关键是提供商，在您的情况下，它是“SSL提供商”，主要问题是连接超时。 If problem was related with "TCP Provider" there could be several reasons related with network etc however in your case it is a security related issue within the connection framework. 如果问题与“TCP提供商”有关，可能有几个与网络相关的原因，但在您的情况下，它是连接框架内的安全相关问题。
Next step to investigate this problem is that on the same machine, you can connect from SSMS to same SQL Database however not from IIS which means the IIS application process is not able to get proper certificate to create the SSL tunnel to create the successful connection. 调查此问题的下一步是，在同一台计算机上，您可以从SSMS连接到相同的SQL数据库，但不能从IIS连接，这意味着IIS应用程序进程无法获取正确的证书来创建SSL隧道以创建成功的连接。 It is possible that you have some log written System Event log so please check there. 您可能有一些日志写入系统事件日志，所以请检查那里。
Because you are using Entity Framework and depend on EF version there are some changed in the connection string so verify if that is what you have: 因为您正在使用Entity Framework并依赖于EF版本，所以连接字符串中有一些更改，因此请验证您是否拥有它：
<add name="MyDatabaseModelEntities" connectionString="metadata=res://*/MyDBModel.csdl|res://*/MyDatabaseModel.ssdl|res://*/MyDatabaseModel.msl;provider=System.Data.SqlClient;provider connection string="data source=abcdefg123.database.windows.net;initial catalog=MyDatabase;persist security info=True;user id=MyDatabaseUser@abcdefg123;password=p@$$w0rd;multipleactiveresultsets=True;Trusted_Connection=False;Encrypt=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
Finally if you are using EF 4.3.1 and connecting to SQL Database please have a look at this article and check if you have similar configuration. 最后，如果你使用的是EF 4.3.1，并连接到SQL数据库，请看看这个文章，并检查是否有类似的配置。
解决方案3
1 2012-09-02 18:00:53
This issue is reported in microsoft connect site here . 此问题已报告Microsoft Connect站点这里 。 Solution is availabel here . 这里有解决方案。 You need to remove non-IFS LSP installed Winsock Catalog Provider. 您需要删除非IFS LSP安装的Winsock Catalog Provider。 Sometimes some software already installed on you machine may cause issue. 有时，您机器上已安装的某些软件可能会导致问题。 In order to remove non-IFS LSP first run the following command on command prompt to see the application causing issue ( ref ) 为了删除非IFS LSP首先在命令提示符下运行以下命令以查看导致问题的应用程序（ ref ）
netsh winsock show catalog > LSP.txt
see the output and analyze the application causing issue and uninstall it. 查看输出并分析导致问题的应用程序并将其卸载。 hopefully it will resolve the issue. 希望它能解决这个问题。
解决方案4
1 2012-12-07 22:02:37
In my case, after trying to repair my VS2012RC couple of times and no luck I chanced upon this link , one of the comments is to do with a third party s/w called 'sendori'. 在我的情况下，在尝试修复我的VS2012RC几次并且没有运气后我偶然发现了这个链接 ，其中一条评论是关于第三方s / w称为“sendori”。 I uninstalled it and all is back to normal in my world. 我卸载它，在我的世界中一切都恢复正常。
解决方案5
1 2013-02-06 16:00:49
Just another tip: SQL server could be out of memory. 只是另一个提示：SQL服务器可能内存不足。 I had this error and when I checked SQL server computer, the SQL service was using 15G of memory, out of 16 total. 我有这个错误，当我检查SQL服务器计算机时，SQL服务使用15G的内存，总共16个。 So restart the service to fix. 所以重启服务以修复。
解决方案6
0 2012-09-01 17:51:25
The problem ended up being vs11 beta. 问题最终成为vs11 beta。
If you have this problem you need to do the following : 如果您遇到此问题，则需要执行以下操作：
1) Uninstall vs11 beta and .NET 4.5 beta 1）卸载vs11 beta和.NET 4.5 beta
2) re-install .NET 4.0 2）重新安装.NET 4.0
Watch everything work again ! 看一切再次运作！
解决方案7
0 2013-02-12 07:48:46
I had same issue with SSMS 2012 but all worked fine on SSMS 2008 on the same box connecting to the same remote server. 我在SSMS 2012上遇到了同样的问题，但是在连接到同一个远程服务器的同一个盒子上，所有这些都在SSMS 2008上运行良好。
Moca.io Proxy was causing trouble for me. Moca.io Proxy给我带来了麻烦。 Uninstalled and all working fine now. 卸载，现在一切正常。 ("remove non-IFS LSP") （“删除非IFS LSP”）
解决方案8
0 2013-05-28 15:11:27
had same problem. 有同样的问题。 In my case uninstalling T-Mobile Web 'n Walk Manager solved problem. 在我的情况下卸载T-Mobile Web'n Walk Manager解决了问题。 Its software for making mobile connection to internet via sim card Josip 它的软件通过SIM卡Josip与互联网进行移动连接
解决方案9
0 2016-03-26 17:20:52
I had this exact error. 我有这个确切的错误。 Solved by setting server not to XXXXXXXXX but to the full domain name XXXXXXXX.YYY.com 解决方法是将服务器设置为不是XXXXXXXXX，而是设置为完整域名XXXXXXXX.YYY.com
Then a message appeared saying encryption was not supported connect without. 然后出现一条消息，说不支持加密连接。
When I did everything worked. 当我做的一切都奏效了。
解决方案10
0 2017-10-15 17:26:51
If you are using dot "." 如果你使用点“。” or partial name of server (without domain name) for data source, please try with actual SQL Server instance name with complete server name. 或者数据源的服务器的部分名称（没有域名），请尝试使用具有完整服务器名称的实际SQL Server实例名称。
解决方案11
0 2023-01-13 17:24:53
In my case:就我而言：
- SQL Server on my local machine on ubuntu docker image SQL 我本地机器上的服务器 ubuntu docker 图片
- connecting via
localhostport1433.通过localhost端口1433连接。
- connecting via
- Connect sucessfully to server from SQL Server Management Studio从 SQL Server Management Studio 成功连接到服务器
- Unable to connect from application.无法从应用程序连接。 Same exception as in OP:与 OP 中的异常相同：
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) (.Net SqlClient Data Provider)
After trying almost everything from this port , I have changed the database host from localhost to 127.0.0.1 and it started working again.在尝试了这个端口的几乎所有内容之后，我将数据库主机从localhost更改为127.0.0.1 ，它又开始工作了。
Not sure if this exactly fixed the issue, but after this change it started working.不确定这是否完全解决了这个问题，但在这个改变之后它开始工作了。 But when I changed it back to localhost it still worked (no exception was thrown).但是当我将它改回localhost时它仍然有效（没有抛出异常）。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.