SQL Server 2017 Developer SQL Server 2017 Enterprise SQL Server 2017 Enterprise Core More…Less
Symptoms
Consider the following scenario:
-
You have an instance of Microsoft SQL Server 2017 that has a server setup that’s linked to another instance of SQL Server.
-
A user without Bypass traverse checking local policy rights runs the first linked server query after a restart of the SQL Server service.
In this scenario, the initial linked server query is run, and every successive linked server query by any user returns error messages that resemble the following:
OLE DB provider «SQLNCLI11» for linked server «server_name» returned message «A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.»
OLE DB provider «SQLNCLI11» for linked server «server_name» returned message «Client unable to establish connection».
Msg 21, Level 16, State 1, Line 0
Encryption not supported on the client
Resolution
This problem is fixed in the following update for SQL Server:
Cumulative Update 12 for SQL Server 2017
About SQL Server builds
Each new build for SQL Server contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for your version of SQL Server:
The latest build for SQL Server 2017
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.
References
Learn about the standard terminology Microsoft uses to describe software updates.
Need more help?
Want more options?
Explore subscription benefits, browse training courses, learn how to secure your device, and more.
Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.
I have tried reinstalling the sqlncl.msi — re-booting etc without success.
I’m on windows vista beta 2 build 5384.
Brand spanking new machine (less that 48 hrs old) and I can’t beleive my bad luck with sql express. My xp pro machine works fine.
Hers’s the error:
TITLE: Microsoft SQL Server 2005 Setup
——————————
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see «How to View Setup Log Files» in SQL Server Books Online.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40×15
——————————
BUTTONS:
&Retry
Cancel
——————————
Here’s the log:
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Professional (Build 5384)
Time : Sat Jul 01 08:01:37 2006
Machine : JOHN-PC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLSupport_1.log
———————————————————————————
Machine : JOHN-PC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLNCLI_1.log
———————————————————————————
Machine : JOHN-PC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SqlWriter_1.log
———————————————————————————
Machine : JOHN-PC
Product : SQL Server Database Services
Error : SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client]Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see «How to View Setup Log Files» in SQL Server Books Online.
———————————————————————————
Machine : JOHN-PC
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}Encryption not supported on the client. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see «How to View Setup Log Files» in SQL Server Books Online.
Error Number : 29515
———————————————————————————
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Sat Jul 01 08:07:48 2006
List of log files:
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_Core(Local).log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLSupport_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQLNCLI_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SqlWriter_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SQL.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_Datastore.xml
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_.NET Framework 2.0.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_Support.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_Core.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_SCC.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_JOHN-PC_WI.log
c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
Some relevant registry settings:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Native Client]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Native ClientCurrentVersion]
«PatchLevel»=»9.00.2047.00»
«Version»=»9.00.2047.00»
«SP»=dword:00000000
«LCID»=dword:00000409
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Native ClientMSIRefCount]
«Uninstall»=»{11111111-1111-1111-1111-111111111111}»
and
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server90]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server90Bootstrap]
«BootstrapDir»=»C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\»
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server90BootstrapMSIRefCount]
«Uninstall»=»{11111111-1111-1111-1111-111111111111},{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F},{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}»
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server90BootstrapSetup]
«PatchLevel»=»9.1.2047»
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerSQLEXPRESS]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerSQLEXPRESSMSSQLServer]
[HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerSQLEXPRESSMSSQLServerSuperSocketNetLib]
«ProtocolList»=hex(7):00,00
SQLSetup0001_JOHN-PC_SQLNCLI_1.log snippet (right at the end) says:
<snipped>
MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client — Configuration failed.
MSI (s) (AC:64) [20:59:38:014]: Product: Microsoft SQL Server Native Client. Version: 9.00.2047.00. Language: 1033. Configuration change completed with status: 1603.
</snipped>
and at the end of SQLSetup0001_JOHN-PC_Core(Local).log
<snipped>
Running: ReportChainingResults at: 2006/5/30 20:59:42
Error: Action «ReportChainingResults» threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1706
Error Code: 0x800706aa (1706)
Windows Error Text: The endpoint format is invalid.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Mon Jan 16 02:06:13 2006
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3245
—- Context ————————————————
sqls::HostSetupPackageInstallerSynch::postCommit
sqls::HighlyAvailablePackage::preInstall
sqls::HighlyAvailablePackage::manageVsResources
ce: 29539
Error: Failed to add file :»C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_JOHN-PC_.NET Framework 2.0.log» to cab file : «C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab» Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/5/30 21:0:8
Message pump returning: 1706
</snipped>
Can anyone advise. I’m willing to take a «you’ll have to re-build your machine» response if I have to. But I just need to know if this really is required.
Thank you,
John.
I found the answer to this elsewhere… Not on Stack Overflow, so I wanted it here for convenience…
When this occurs, in regards to a linked server, it is due to the fact that the encryption required by the target server doesn’t match that of the requesting server, so connection could not be established.
To remedy this issue, you can attempt to uninstall everything SQL related on your machine and reinstall… Or you can attempt the following:
- Using Command Prompt / Powershell / Cortana, type, ‘regedit’ and hit enter.
- In ‘Registry Editor,’ navigate to this location… ‘HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftMSSQLServerClientSNIxx.x’ (The ‘x’s represent your version of SNI… «Sql Network Interface»)
- Backup the folder at the following location first, by clicking, ‘File/Export’ and save it wherever, ‘HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftMSSQLServerClient’
- Whatever version of SNI you have, in my case 11.0, you will do a file level search and replace, in the file data below, for SNIxx.x, replacing the version number with your’s.
- Now in Registry Editor, click, ‘File/Import’ and navigate to the folder where you’ve saved your new file, double click it, or highlight it and click, ‘open’.
Here is the data which needs to exist in that file…
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClient]
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientConnectTo]
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientDB-Lib]
"AutoAnsiToOem"="ON"
"UseIntlSettings"="ON"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.x]
"ProtocolsSupported"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,
00,00,00,76,00,69,00,61,00,00,00,00,00
"ProtocolOrder"=hex(7):73,00,6d,00,00,00,74,00,63,00,70,00,00,00,6e,00,70,00,
00,00,00,00
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xGeneralFlags]
"NumberOfFlags"=dword:00000002
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xGeneralFlagsFlag2]
"Label"="Trust Server Certificate"
"Value"=dword:00000000
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xLastConnect]
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xnp]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000001
"ProtocolName"="Named Pipes"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xnpProperty1]
"Name"="Default Pipe"
"Value"="sql\query"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xsm]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000000
"ProtocolName"="Shared Memory"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xtcp]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000003
"ProtocolName"="TCP/IP"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xtcpProperty1]
"Name"="Default Port"
"Value"=dword:00000599
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xtcpProperty2]
"Name"="KEEPALIVE (in milliseconds)"
"Value"=dword:00007530
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xtcpProperty3]
"Name"="KEEPALIVEINTERVAL (in milliseconds)"
"Value"=dword:000003e8
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xVIA]
"DLLname"="SQLNCLI"
"NumberOfFlags"=dword:00000000
"NumberOfProperties"=dword:00000002
"ProtocolName"="VIA"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xVIAProperty1]
"Name"="Default Server Port"
"Value"="0:1433"
[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftMSSQLServerClientSNIxx.xVIAProperty2]
"Name"="Default Client NIC"
"Value"="0"
We have an issue while installing the Microsoft SQL Server 2014 and took us almost 5 hours to sort it out. So, the issue is we cannot bring up the SQL Server Agent service even though the SQL Server service is running fine.
From the error log location (C:Program FilesMicrosoft SQL Server[SQL-VERSION]MSSQLLog, the trace file SQLAGENT gave us this,
Microsoft SQLServerAgent version 12.0.4419.0 (X64 unicode retail build) : Process ID 5264 The SQL Server Agent startup service account is ITSITI. SQL Server does not accept the connection (error: 817). Waiting for Sql Server to allow connections. Operation attempted was: Verify Connection On Start. Unable to connect to server '(local)'; SQLServerAgent cannot start SQLServer Error: 21, Encryption not supported on the client. [SQLSTATE 08001] SQLServer Error: 817, SSL Provider: The client and server cannot communicate, because they do not possess a common algorithm. [SQLSTATE 08001] SQLServer Error: 21, Client unable to establish connection [SQLSTATE 08001] SQLServer Error: 817, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] Logon to server '(local)' failed (DisableAgentXPs) SQLServerAgent terminated (normally)
In the Windows Event Viewer,
TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.
TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.
Solution
Refer to this Microsoft article, TLS 1.2 support for Microsoft SQL Server and perform the update based on current SQL server version installed.
Alternatively, you can perform the below workaround. But, updating the SQL server is always be the recommended way.
Open the Registry Editor and go to the below directory and ensure the DisabledByDefault and Enabled value as below for client and server.
HKEY_LOCAL_MACHINESYSTEMControlSet001ControlSecurityProvidersSCHANNELProtocolsTLS 1.0Client
HKEY_LOCAL_MACHINESYSTEMControlSet001ControlSecurityProvidersSCHANNELProtocolsTLS 1.0Server
Reference
- TLS 1.2 Support for SQL Server 2008, 2008 R2, 2012 and 2014
Problem
Unable to process cubes with a remote Microsoft SQL Analysis Services database for Case Foundation Case Analyzer due to error 08001; Encryption not supported on the client .
Symptom
While installing Case Foundation Case Analyzer and configuring the Microsoft Analysis Services database on a remote server the following error is seen in the pesvr_system.log file when attempting to process the cubes:
RPCHandler b055bab8 [Error] Case Analyzer — Cube processing failed for store Concord Case Analyzer. Excepton:
java.lang.Exception: OLE DB error: OLE DB or ODBC error: A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.; 08001;
Client unable to establish connection; 08001; Encryption not supported on the client.; 08001.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘VMAE’, Name of ‘VMAE’.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘Queue’, Name of ‘Queue’ was being processed.
Cause
As this is a remote Microsoft Analysis SQL Server database the DataSource Service Provider needs to be changed from the default «Native OLE DBSQL server Native Client 11.0» to «Microsoft OLE DB Provider for SQLServer»
Resolving The Problem
1. Open Microsoft SQL Server Studio.
2. Connect to the Analysis Services database as the CA Admin user.
3. Maximise the Case Analyzer OLAP database.
3. Maximise the DataSources folder.
4. Right click on the DataSources — VMAE option and choose Properties.
5. Click on the three dots on the line that shows the Connection string Provider.
6. On the Provider drop down change it from «Native OLE DBSQL server Native Client 11.0» to «Microsoft OLE DB Provider for SQLServer»
7. Re-enter the server and database information on the Configuration screen and click ok.
8. Restart the Microsoft Analysis SQL Server services under Services.
9. Attempt to process the cubes.
[{«Product»:{«code»:»SSTHRT»,»label»:»IBM Case Foundation»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud & Data Platform»},»Component»:»Case Analyzer»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»5.2.1;5.2.1.1″,»Edition»:»All Editions»,»Line of Business»:{«code»:»LOB45″,»label»:»Automation»}}]