This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 45%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
We are using Microsoft SQL Server 2016 (13.0.4001.0). Our client application connects using old ODBC drivers "SQL Server" (SQLSRV32.DLL). Recently Microsoft released cumulative update KB5019959 for Windows 10. After installing this update, our client application cannot connect to the SQL Server. Error received:
DIAG [08S01] [Microsoft][ODBC SQL Server Driver]Communication link failure (0)
If we uninstall the update, it started to work again. In this update, the SQLSRV32.DLL is updated to version 10.00.19041.2251 (before the update, it was 10.00.19041.2130).
If we downgrade the SQLSRV32.DLL back to version 2130, it works again.
There was nothing else changed.
So, why is this KB5019959 causing this issue with odbc connection to SQL Server? Is there any special configuration or whatever which we need to set? Because of this update, our client application is broken.
Hi
Go To Sql Server confgration Manager
Sql Server Network configuration
Prootocols for SQLEXPRESS:
Change Named Pipes to Enabled
change Tcp/ip to Enabled
after restart your pc.
cd C:\Windows\SysWOW64
run odbcad32
config odbc
Best regards.
Hi @n03z ,
May I ask did you try downloading the latest version of ODBC? And you can download from this link: https://learn.microsoft.com/en-us/sql/connect/odbc/download-odbc-driver-for-sql-server?view=sql-server-ver16
To you description, the patch leads to your problem. If you want to know the detail of this error you may need to check the upgrading information of this patch. And in my opinion, I think maybe your version of ODBC is not compitale for the patch (it's just a guess)
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment"
You are referring different odbc driver. That driver in the link you provided, it doesn't install/update SQLSRV32.DLL. In fact, I tried installing the latest version 18, that doesn't resolve the issue (because it is different driver, which the client application doesn't use it). So, that's not the answer.
The issue is very specific to this KB5019959, because installing it would break SQLSRV32.DLL functionality.
Uninstalling KB5019959 would resolve the issue. There is nothing else.
So, why is that and what's special with this KB5019959 related to SQLSRV32.DLL. Are there any requirements we need to adapt in the Windows environment? Or we need to adapt in the client application code?
Uninstalling KB5019959 should not be acceptable solution.
Hi @n03z ,
In my opinion this needs to check the KB5019959 in detail ,which will make this quetion become a windows problem. So the advice I can give you is try installing the SQL on the virtual disk to change the environment now that you can't neither rollback or upgrade. Hope this can be helpful for you.
And that's the problem. There is nothing I could found from KB5019959 which show details on what has been changed or need to be adapted. All I found were what has been fixed by that KB. So yeah, that's why we are now left in the dark with broken application just by installing this KB5019959. Uninstalling it would make it work again.
Hi @n03z ,
Yes I'm agree with you this is a windows problem, you can try making a new post in the windows fourm to seek their help. Windows group must know the detail about KB5019959
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(51.2, 22%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETW%3C/text%3E%3C/svg%3E)
I am also having the same issues with this new Security Update. We have a proprietary software that isn't working anymore. We can send data to the database via the software, but it cannot read data from the database. It's a total head-scratcher, and we're doing the same thing, uninstalling the update, and it works fine again.
Just uninstall your sql server and do the following steps to install correct way
Installing SQL Server 2016
Launch the SQL Server installer from CD or file download.
Click System Configuration Checker. This will launch and run a tool that checks for conditions on your server that could prevent SQL Server from installing.
When the tool launches, click the Show details button. A successful scan should look like the one shown below. If you encounter any issues, look at the detailed report, resolve the reported issues, and rerun the scan.
Click OK when done to return to the “SQL Server Installation Center” window.
In the “SQL Server Installation Center” window, click Installation then New SQL Server stand-alone installation or add features to an existing installation
Enter your product key and click Next.
Check the I accept the license terms. checkbox and click Next.
Wait for the Rule Check to run.
At the “Microsoft Update” step, check Use Microsoft Update to check for updates (recommended) unless your software update process does not utilize automatic updates from Microsoft and click Next.
At the “Product Updates” step leave all defaults and click Next.
Wait for the “Install Setup Files” step to complete. Check that all operations pass. When the installation is successful, click Next.
The only feature in “Feature Selection” necessary for Secret Server is “Database Engine Services.”
Unless you are using Geo-Replication, you can leave everything else unchecked. Leave the directory locations unchanged and click Next.
At the “Instance Configuration” step leave “Default instance” selected.
Choose a name (Instance ID) for your SQL Instance, then click Next.
At the “Server Configuration” step leave the defaults and click Next.
In the Database Engine Configuration window, you have the choice to select either Windows authentication mode or Mixed Mode. Select the option that will work best for your environment. See descriptions below:
a. Mixed Mode (for easiest configuration) Mixed Mode is required if you intend on using a SQL Server account to authenticate Secret Server to your SQL Server instance. We recommend using Mixed Mode if you are setting up a test or demo environment. Selecting this option will also require you to set a password for the SQL Server system administrator (sa) account. See Adding a SQL Server User (section below) for instructions on adding more users.
b. Windows Mode (recommended for best security) This will prevent SQL Server account authentication. We recommend using Windows Mode for production environments. Whatever user or group assigned will have administrative access to your SQL instance. According to Best Security Practices, limit this number to as few users as possible.
Note: If choosing Windows Mode you will also need to set up a service account to run your Thycotic product IIS Application Pool(s) later in the installation process.
Note: **Select an Administrator account to manage your SQL Server Database.
You can leave the options in the remaining tabs at their default values or change the file locations in the “Data Directories” and “TempDB” tabs if you wish to store the database and log data in a different drive or directory. Click Next.
Wait for the setup wizard to progress to the “Ready to Install” step and click Install.
Wait for installation to complete. This may take several minutes. Click Close.
Installing SQL Server Management Studio
Back in the “SQL Server Installation Center” window, click Installation then Install SQL Server Management Tools
Wait for the web page to load then click the Download SQL Server Management Studio 17.5 link (note: actual version # may be different if a newer version is available).
After the download is complete, click Run (if using Internet Explorer to download the file; if using a different browser, follow the conventions for that browser to run the file or open the download folder and run the file).
Click Install when the SQL Server Management Studio installer starts.
Wait for the installer to complete. This may take several minutes. When the installation has completed, click Restart if prompted. Otherwise, click Close and then close “SQL Server Installation Center.”
Creating the SQL Server Database
To install Secret Server or Privilege Manager, the Thycotic installer will create the SQL database for you if it does not exist and if the user account has permission to create a new database (this requires the dbcreator server role).
If not using the Thycotic Installer, use the following steps to create a database manually through SQL Server Management Studio:
Open SQL Server Management Studio by searching for it from the Windows Start screen.
Connect to your SQL Server instance.
Right click the Databases folder and select New Database…
Enter a name for your database in the Database name field, and then click OK.
Adding a SQL Server User
According to Security Best Practices, limit the number of users with access to your SQL database as much as possible.
Use the following instructions to add a SQL Server account for Secret Server to use to access the SQL database:
Open SQL Server Management Studio by searching for it from the Windows Start screen.
Connect to your SQL Server Database.
Expand the Security folder.
Right-click the Logins folder and select New Login…
Select a method of authentication:
a. SQL Server Authentication Use this option to create a new SQL Server account (this requires Mixed Mode to be enabled). To create the account, enter a new username and password and then deselect the Enforce password policy check box to prevent the account from expiring.
b. Windows Authentication Use this option to add access to SQL Server for an existing Windows account. To add the account, enter the login name or click Search to find the account. It is recommended to use a domain account rather than a local Windows account.
Click User Mapping in the left menu.
Select the check box next to your Secret Server database.
In the Database role membership window, select the db_owner check box.
Click OK.
There is no issue with the SQL Server 2016, the server part. I have updated with SP3 and it doesn't resolve the issue.
Please read the problem description, the issue is closely related to installing the KB5019959 which break SQLSRV32.DLL functionality.
If the KB5019959 is uninstalled, the issue would be resolved.
So, the question is why this KB5019959 break SQLSRV32.DLL? What's special in it? Is there any new requirements?
So, the question is why this KB5019959 break SQLSRV32.DLL? What's special in it? Is there any new requirements?
@n03z , my guess is there was a change to the WDAC components in the Windows update, possibly related to TLS. The legacy drivers included with Windows have not had functional updates in nearly 20 years. You'll have more control if you use a newer driver instead of the one included with the OS. This may be as simple as a change to the connection string or DSN once the newer driver is installed.