Summary
Recommendations when legacy cryptographic protocols are disabled.Synopsis
If legacy cryptographic protocols are disabled the installer may be unable to create a database connection. For example, under particular circumstances you may be using Windows 2008 R2 (and above) which has support for TLS 1.2. This implies you are working with what Microsoft addressed in SQL 2014 SP1?s support for TLS 1.2 in its CU1 update. When you run the installer with default SQL Connection settings created by InstallShield at runtime there is error:There was an error logging in to Microsoft SQL Server. Error: [DBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error. (18)
Discussion
This applies to Basic MSI project types.In the scenario presented the legacy TLS 1.0 and TLS 1.1 (and prior SSLs) are all disabled. Disabling cryptographic protocols is commonly done in GPO (Group Polciy Object) or the Registry.
Using InstallShield the default settings may not meet your needs. To address this connection problem you can change the driver name in the AdoDriverName column of the ISSQLDBMetaData table using the Direct Editor so that you can use a different driver for InstallShield to establish a connection.
To address the situation trying to support TLS 1.2 using the Direct Editor set the property to "sqlncli11". It is expected you can only specify one driver name at a time.
If you continue to have an issue you might be able to audit the login via a SQL Tool such as "SQL Server Profiler", which reports all activity on a SQL Server. SQL Server Profiler is a rich interface to create and manage traces and analyze and replay trace results. Reference:
SQL Server Profiler
Workaround
Steps to configure your InstallShield installation project so that your installation uses the SQL Server Native Client 11 ODBC driver:- In the View List under Additional Tools, click Direct Editor.
- In the Tables explorer, click the ISSQLDBMetaData table.
- In the ISSQLDBMetaData column, find the MSSQLServer row.
- Replace the value of the AdoDriverName column with the following:
sqlncli11
Additional Information
Please see the HelpNet article:Requirements for Connecting to Instances of SQL Server Express LocalDB
Related Documents
See the Microsoft Blogs:SQL Server Release Services
SSL Security error [DBNETLIB]ConnectionOpen (SECDoClientHandshake())
Article:
TLS 1.2 support for Microsoft SQL Server . This article provides information about the updates that Microsoft is releasing to enable TLS 1.2 support for SQL Server 2016, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. This article also lists supported client providers.
Was this helpful?
Related Articles
Analytics/Cognos connection to SQL server fails when server is configured to use TLS 1.2 6Number of Views Cognos error: QE-DEF-0322 The connection string is invalid. RQP-DEF-0068 Unable to connect to at least one database during… 28Number of Views Error 27502. Could Not Connect To Microsoft SQL Server Using TLS 1.2 (Transport Layer Security 1.2) 134Number of Views Unable to Create Connection to Mail Server From FlexNet Operations 7Number of Views Issue connecting to SQL database with "SSL Security Error" error after enabling TLS 1.2 and disabling TLS 1.0 and TLS 1.1 … 9Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago