Control Compliance Suite Agent Content Update (ACU) installer for MS SQL restarts the MS SQL Server service in the process of content update

Products

• Control Compliance Suite Exchange

Issue/Introduction

 

Resolution

We want to inform you about an issue, which we observed in MS SQL Server Agent Content Update (ACU) released recently with Security Content Update (SCU) for Control Compliance Suite.

To support data collection in TLS 1.2-enabled MS SQL Servers, Control Compliance Suite Agent Content Update (ACU) installer (TPK) is updated in SCU 2018-3 (for Control Compliance Suite 11.5.x) and SCU 2019-1 (for Control Compliance Suite 12.X) and now the TPK carries an installer for the latest available version of Microsoft® SQL Server® 2012 Native Client (SNAC). In specific cases, when TPK installer upgrades the existing SNAC client to the required version, the SNAC client installer msi (which is invoked silently by the TPK installer) forces the MS SQL Server service to restart.

This issue is not observed if you are installing SNAC client for the first time or if the existing SNAC client is at the required version.

We recommend you to provision downtime for SQL servers if you are upgrading the MS SQL ACU for SCU 2018-3 for Control Compliance Suite 11.5.x agents or SCU 2019-1 for Control Compliance Suite 12.x agents.

You need to be cautious about this issue if:

• You are using Agent based data collection for MS SQL Server hosted on any of the following Windows versions:
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2.
• Your MS SQL Server host machine has lower version of Microsoft® SQL Server® 2012 Native Client than the latest available version.
• You are upgrading Control Compliance Suite agent content manually on MS SQL Server or remotely using ACU job from Control Compliance Suite console.

You need not worry about this issue if you have:

• MS SQL Server installed on Windows Server 2016
• Your MS SQL Server already has the required version of Microsoft® SQL Server® 2012 Native Client installed.
• You do not have Microsoft® SQL Server® 2012 Native Client installed.