DRDA server crashes when Java client connects by using DB2XADataSource class. Status. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Resolution. This issue is fixed in the following cumulative update for Host Integration Server: Cumulative Update 4 for Host Integration ...

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component.

This update provides support for Transport Layer Security (TLS) 1.1 and TLS 1.2 in Windows Server 2012, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1.

This article describes a problem in which DNS client API call fails and could lead to service restart freeze in Windows Server 2012 R2 or Windows Server 2012. An update is available to fix this issue. Before you install this update, see the Prerequisites section.

MS10-081: Vulnerability in the Windows common control library could allow remote code execution - Microsoft Support. Windows 7 Enterprise Windows 7 Home Basic More... Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011.

This issue occurs because the SQL Server engine cannot handle login records when SSL data is split into multiple Tabular Data Stream (TDS) packets. Resolution Service pack information for SQL Server 2008 R2. To resolve this problem, obtain the latest service pack for SQL Server 2008 R2.

When you use AlwaysOn Availability Group, Database Mirroring, or Service Broker in Microsoft SQL Server, the encrypted endpoint communication with Transport Layer Security (TLS) protocol version 1.2 fails. Additionally, you receive the following error message in the SQL Server Error log: Connection handshake failed.

May 8, 2018. An update to change the default setting from Vulnerable to Mitigated. Related Microsoft Knowledge Base numbers are listed in CVE-2018-0886. By default, after this update is installed, patched clients cannot communicate with unpatched servers.

Symptoms. You cannot connect to a server that is running Microsoft SQL Server 2014 or SQL Server 2012 by using the Transport Layer Security (TLS) protocol version 1.2. Additionally, the following error message is logged in the SQL Server error log: TDSSNIClient initialization failed with error 0x80090331, status code 0x80.

KB3216543 - FIX: Workloads that utilize many frequent, short transactions in SQL Server 2016 and 2017 may consume more CPU than in SQL Server 2014 - Microsoft Support.