Provider ssl provider error 0 время ожидания операции истекло

• Remove From My Forums

• Вопрос

• Неожиданно перестала подключаться Management studio к серверу.

  Сообщение об ошибке:

  Не удается подключиться к tst-db-2k5-01.

  ===================================

  Подключение к серверу успешно установлено, но затем произошла ошибка в процессе подтверждения, предшествующего входу. (provider: SSL Provider, error: 0 — Время ожидания операции истекло.) (.Net SqlClient Data Provider)

  ——————————
  Чтобы получить справку, щелкните: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=258&LinkId=20476

  ——————————
  Имя сервера: tst-db-2k5-01
  Номер ошибки: 258
  Серьезность: 20
  Состояние: 0

  ——————————
  Расположение программы:

     в System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
     в System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
     в System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)
     в System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
     в System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
     в System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
  timeout)
     в System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
     в System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
  SqlConnectionString userConnectionOptions)
     в System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
     в System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
     в System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
     в System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
     в System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
     в System.Data.SqlClient.SqlConnection.Open()
     в Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
     в Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

  ===================================

  Время ожидания операции истекло

  Тип аутентификации: проверка подлинности Windows.

  Переустановка SQL Server management studio 2012 не помогает.

  Как можно восстановить нормальную работу?

  • Изменено

    21 ноября 2013 г. 7:52

Problem

System was initially working OK (no problems/errors).

Customer then modifies the Microsoft networking TLS settings (on both the Controller application server and SQL database server) so that:

• TLS 1.0 disabled
• TLS 1.1 disabled
• TLS 1.2 enabled

After making those changes, user launches Controller client. User then:

• Chooses database
• Types in username/password

An error appears.

Symptom

System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 — An existing connection was forcibly closed by the remote host.) —> System.ComponentModel.Win32Exception: An existing connection was forcibly closed by the remote host
   — End of inner exception stack trace —
   at Cognos.Controller.Proxy.ControllerReportNetService.RepNet.GetUserInfo(String sGuid, String sUser, String passportId)
   at Cognos.Controller.Proxy.CCRWS.GetUserInfo(String sGuid, String sUser, String passportId)
   — End of inner exception stack trace —
   at Cognos.Controller.Forms.Common.Main.DoLoginCognos8(Form& frm)
   at CCR.AppContext.DoLogin()
   at CCR.AppContext.Login()

Cause

The Controller application server cannot connect to the Microsoft SQL database server.

Example

In one real-life customer scenario, the cause was Microsoft patch KB4467697  (on the Controller application server).

Resolving The Problem

Fix:

Uninstall the Microsoft patch KB4467697 from the Controller application server:

Workaround:

Re-enable the TLS 1.0/1.1 protocols (on both the Controller application server and SQL database server).

Related Information

Document Location

Worldwide

• 
  Вопрос задан

  более трёх лет назад
  

• 5650 просмотров

Пригласить эксперта

• 
  Показать ещё
  Загружается…
  

I said earlier that I have bunch of *good* friends who remember me whenever they get any issue with SQL Server. So I got a call from my friend and he told that he is not able to connect to SQL Server from some client. Since it’s only few client, we can easily rule out the issue with SQL Engine not allowing connection. I asked him to connect via SQL Server Management Studio and got below error.

TITLE: Connect to Server
——————————
Cannot connect to SQLDBServer.
——————————
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 – The token supplied to the function is invalid) (Microsoft SQL Server, Error: -2146893048)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-2146893048&LinkId=20476
——————————
BUTTONS:
OK
——————————

Did basic troubleshooting as below

• Tested basic connectivity like ping, telnet etc. everything is working fine, except the connection to SQL engine from this machine.
• Error message says SSL but there was no certificate used in SQL Server.
• There was no certificate used.

Next major task is to find out what is the difference in both servers. So I asked him what were the things done on “bad” client. He said that he applied bunch on Windows updates. Looking at list I found one which talks about SSL.

http://support.microsoft.com/kb/2643584 (MS12-006: Vulnerability in SSL/TLS could allow information disclosure: January 10, 2012)

We check the machines and found that SendExtraRecord was 1 on “bad” client whereas other “good” clients it was 2.

Here were the steps taken to solve the issue. (taken from KB)

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following subkey in the registry:

   HKEY_LOCAL_MACHINESystemCurrentControlSetControlSecurityProvidersSCHANNEL

3. On the Edit menu, point to New, and then click DWORD Value.
4. Type SendExtraRecord for the name of the DWORD value, and then press Enter. 
5. Right-click SendExtraRecord, and then click Modify.
6. In the Value data box, type 2 to disable the split record in schannel, and then click OK.
7. Exit Registry Editor.

In our case it was 1 and making it 2 fixed the issue and were were able to covert bad clients to good clients.

Hope this helps.

Cheers,
Balmukund