This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- TLS 1.2 support in IS 2018 ?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Nov 26, 2018
06:04 AM
TLS 1.2 support in IS 2018 ?
Hi,
Does Installshield 2018 support TLS 1.2 environment where i can execute sql scripts using "SQL scripts" feature of InstallShield ?
Does Installshield 2018 support TLS 1.2 environment where i can execute sql scripts using "SQL scripts" feature of InstallShield ?
(4) Replies
‎Dec 03, 2018
02:18 AM
‎Dec 05, 2018
03:26 AM
Larry578 wrote:
we are in same boat. please help me, if you find any thing related to this query. and I also not able to update TLS 1.1 to TLS 1.2. Suggest me how can I do this?
Hi Larry,
If you are using setup.exe, you can add a new pre-requisite for installing Microsoft latest MSOLEDBSQL driver and update the AdoDriverName coumn to 'msoledbsql' in ISSQLDBMetadata table.This should fix issue for TLS 1.2 and later environments.
Let me know if you find any other alternatives..
‎Nov 22, 2023
02:58 AM
Hi Vivek,
I tried what you suggested but it didn't work. I am using Install shield 2020 R3 and MSSQL server to connect. Do you have any alternate solution which may work
‎Feb 15, 2019
03:07 PM
vivekjazzwal wrote:
Hi Larry,
If you are using setup.exe, you can add a new pre-requisite for installing Microsoft latest MSOLEDBSQL driver and update the AdoDriverName coumn to 'msoledbsql' in ISSQLDBMetadata table.This should fix issue for TLS 1.2 and later environments.
Let me know if you find any other alternatives..
The solution we used (in IS2015) was to direct edit the SQLServer ISSQLDBMetaData from the oledb driver to the newer driver "sqlncli11". The line should look like:
We had to manually insure the right version of the native driver because the IS pre-req version wasn't adequate..