The IM Manager installer uses the registry key 'HKEY_CURRENT_USER SOFTWARE Microsoft Microsoft SQL Server 80 Tools Service Manager' to see if MSDE is installed. If the registry key is not present MSDE is stopped and does not start again during the upgrade. Exception Details: System.Runtime.InteropServices.COMException: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Source Error: The source code that generated this unhandled exception can only be shown when compiled in debug mode. SECDoClientHandshake() SSL Security error connecting SQL Server when installing Dynamics CRM Server 2016. 1) Go to SSCM( SQL Server Configuration Manager ), click “protocols for ”, you can see the status of each protocol that server support. 2) Look at server ERRORLOG file. - Key words indicates server shared memory is enabled. Dec 12, 2008  Please verify SQL Server is running and check your SQL Server registration properties(by right-clicking on the (LOCAL) node) and try again. When i checked ran the SSL Diagnostics, it gave me the following error. [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. So either the server you're trying to connect to is specified incorrectly, isn't contactable or is refusing the connection.

SSL Security error [DBNETLIB]ConnectionOpen (SECDoClientHandshake())


This particular resolution is one of its own kind their could have been other possibilites for his error message to raise, generally it comes if you have Expired Certificates or invalid Certificates on the Server for the user account or the computer account, delete the unwanted Certificates on the server and then try to start SQL or Connect should work
Other times this message comes if you had encryption enabled for the Server sometime but no more now, but then internally we are still finding the certificate somehow, though you anyways dont need the SSL certificate, so go to the following Registry and check for the Certificate value it should be EMPTY, but if it has ThumbPrint value of the Certifcate it is a problem, go ahead and make the change for Certificate value set to 0
HKLMSOFTWAREMicrosoftMSSQLServerMSSQLServerSuperSocketNetLib REG_SZ Certificate=0
Coming back to this unique problem:
Problem Description:
Trying to enable SSL encryption for sql server connections on server
Went through the steps detailed in article 276553 (http://support.microsoft.com/?id=276553).
From one client we were unable to connect to the SQL Server 2000 using encrypted connections {forced encryption from the Client configuration, this client box where its working is a Windows 2003 SP1 box}. From our own desktop workstation {Windows XP sp2}, along with that of one of the other Clients box {Windows 2000} they are unable to connect to the SQL Server through encrypted connections.
Consistently receive the following error:
[DBNETLIB]SSL Security error[DBNETLIB]ConnectionOpen (SECDoClientHandshake()).

We have checked and re-checked and re-re-checked that his local workstation trusts the same root certificate authority (plus all intermediary issuing authorities) as does the SQL Server

The certificate chains are identical on both machines.
We Enabled odbc tracing and attempted to login again from his local box. The log of that attempt is enclosed. It contains the following information:
osql -Sact-dd01 2764-1a88 EXIT SQLDriverConnectW with return code -1 (SQL_ERROR) HDBC 009A1830 HWND 00000000 WCHAR * 0x74329A38 [ -3] '****** 0' SWORD -3 WCHAR * 0x74329A38 SWORD 2 SWORD * 0x00000000 UWORD 0
DIAG [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error (18)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (SECDoClientHandshake()). (271)
Operating System:Windows 2003 : where the Encrypted Client connections are working
Operating System: Windows XP Sp2 and Windows 2000 SP4 where the Client connections are not working using Encryption, though if the encryption is not enabled the connections will flow fine
Cause

The cause is a DBNETLIB.DLL {Remember this is not a COM DLL}, the version compatibility of this DLL on the XP and Windows 2000 is the possible culprit, i dont think it is a BUG
Resolution

1) Check the for the following DLL's version on the Windows 2003 SP1 or SP2 Box

C:WINDOWSsystem32DBNETLIB.DLL
Version: 2000.86.1830.0 {Windows 2003 SP1}
2) Now Check the Version for the same DLL on the Windows XP Sp2 and Windows 2000 Sp4 box

In My case the Windows XP SP2 had the following version of the DBNETLIB.DLL
Version: 2000.85.1117.0
3)

The Windows 2000 SP4 box had the follwoing DLL version in my case
Version: 2000.85.1064.0
4) So what i did was, i copied the DLL Version: 2000.86.1830.0 from the Windows 2003 SP1 box to the Windows Xp SP2 box and also to the Windows 2000 SP4 Box
Went to the following location on the Windows XP Sp2 box:

C:windowssystem32 and renamed the existing DBNETLIB.DLL to DBNETLIB.DLL.OLD
After that pasted the copied DLL version 2000.86.1830.0 on the XP Sp2 box in the following location c:windowssystem32DBNETLIB.DLL {2000.86.1830.0} after that did a refresh and saw that the Version got back to the older version that is 2000.85.1117.0. Made a check in the DLLCACHE {c:windowssystem32DLLCACHE} and saw that the DBNETLIB.DLL was present there and was having the Version 2000.85.1117.0 {so whenever the connection was made, this DLL from the cache was picked}, hence First paste the DBNETLIB.DLL {with version 2000.86.1830.0} in the DLLCACHE and then replace the actual DLL inside the c:windowssystem32.
Do a refresh and see if the DLL version is Showing as 2000.86.1830.0 on the XP Sp2 Box.

After this again try to connect to the SQL Server from this Client box {Make sure that Force Encryption is Checked in the Client Configuration}
The above resolved the issue with the SSL encryption errors, and the Secured channel is established
5) Repeat the above Steps for a Windows 2000 SP4 box, and this should help in getting past through the problem
NOTE: Never try to Register this DLL, also it wont let you as well, as it is not a COM DLL, also replacing this DLL will never break anything as it is a System DLL and the version is upgraded through MDAC
Posted by2 years ago
Archived

Okay - so I've been banging my head against the desk for a bit on this one. We finally isolated the issue but I'm hoping that someone here has some guidance on how to proceed. We're in the process of building our new 16xx infrastructure to replace 2012r2 (we're planning on a clean install rather than an upgrade to take advantage of this opportunity to clean up our library and source folders).

For all intents and purposes our environment looks like this:

  • Single Primary Server

  • Windows Server 2012r2

  • SQL Server 2014 SP2 CU2

While we do have multiple DPs they don't factor into this particular part of the conversation.

When we went to install SCCM in our 'clean' environment - we were presented with the following error message:

Normally I'd assume it was related to SQL version, but we were at the latest. ConfigMgrSetup.log reported the following:

It dawned on my SQL dba that we had disabled SSL v2/v3 on the servers, but we had also disabled TLS 1.0. Working through the list from top down we found that re-enabling TLS 1.0 allows the install to continue. However, we don't really want to consider that as a 'solution'.

I was able to install the 'ODBC Driver 11 for SQL Server' and trick ODBC into using that in place of the 'SQL Server' driver that comes stock with the OS. This allowed the installation to progress as well - but I'm also not comfortable with that solution. I'm assuming there are some vast differences in APIs available in that driver vs the stock SQL driver.

My assumption is that the stock SQL driver does not support TLS 1.1 or 1.2, but I'm not sure how I can force the installer (and SCCM for that matter) to use the newer ODBC driver from Microsoft without hacking the registry to trick the OS.

Has anyone else encountered a similar issue? Did you find a solution other than enabling TLS 1.0?

EDIT: I should also state for the record that even with TLS 1.0 disabled, SSMS still works remotely - so I know it's not related to the SQL services not starting as outlined in numerous articles surrounding TLS 1.0 and SQL 2014.

Odbc Sql Server Driver Shared Memory Ssl Security Error

EDIT For those of you with a lab who would like to reproduce the issue:

  • OS: 2012r2 with all available updates

  • SCCM Media: mu_system_center_configuration_manager_version_1511_x86_x64_dvd_7295963.iso

  • although this seems to also affect the 1606 media from MSDN as well

  • SQL Server: 2014 with SP2 installed, and then updated with CU2

  • Default Instance (MSSQLSERVER)

  • Separate domain service accounts for 'SQL Server (MSSQLSERVER)', 'SQL Server Agent (MSSQLSERVER)', 'SQL Server Integration Services 12.0', and 'SQL Server Reporting Services (MSSQLSERVER)'

  • sysadmin rights given to group which includes the account installing SCCM

  • IISCrypto (available from: https://www.nartac.com/Products/IISCrypto) with the following settings:

This should be all that is necessary to reproduce the errors I'm seeing above.

I was able to 'hack' past the preflight check by:

Ora-04031 Unable To Allocate Shared Memory

Server

Odbc Sql Server Driver Shared Memory Ssl Security Error Code

  • Installing Microsoft ODBC Driver 11 for SQL Server: https://www.microsoft.com/en-us/download/details.aspx?id=36434

  • Modifying the following registry keys as follows:

    May 11, 2015  Watch League of Legends 50k Riot Points Hack Unlock All Champions skins - champions league 2014 on dailymotion. LEAGUE OF LEGENDS HACK LEVEL 30 + ALL CHAMPIONS UNLOCKED+ALL SKINS(). League of Legends 50k Riot Points Hack Unlock All Champions skins. Lol unlock all skins hack.

  • HKLMSOFTWAREODBCODBCINST.INISQL ServerDriver = c:Windowssystem32msodbcsql11.dll

  • HKLMSOFTWAREODBCODBCINST.INISQL ServerDriverODBCVer = 03.80

  • HKLMSOFTWAREODBCODBCINST.INISQL ServerSetup = c:Windowssystem32msodbcsql11.dll

  • HKLMSOFTWAREWow6432NodeODBCODBCINST.INISQL ServerDriver = c:Windowssystem32msodbcsql11.dll

  • HKLMSOFTWAREWow6432NodeODBCODBCINST.INISQL ServerDriverODBCVer = 03.80

  • HKLMSOFTWAREWow6432NodeODBCODBCINST.INISQL ServerSetup = c:Windowssystem32msodbcsql11.dll

However, I'm not confident that this is a 'good' solution, since it's expecting a different revision of the driver that may have different APIs.

Odbc Sql Server Driver Shared Memory Ssl Security Error Windows 10

6 comments