FIX: Launchpad services fails to start during failover in SQL Server 2019

Applies to: SQL Server 2019 on Windows

Symptoms


Assume that you try to install a SQL Server failover cluster that has the Machine Learning Services and LanguageExtension features enabled on an instance of Microsoft SQL Server 2019. This SQL Server instance has twomodes of deployment: Integration Installation with Add Node and Advanced/EnterpriseInstallation. For the Advanced/Enterprise Installation, a bug in thecomplete installation step prevents the Launchpad services from starting after afailover occurs.

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 SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Note Since the fix is part of the SQL Server setup, the CU setupis needed for the fix to take effect. You can do this in one of the following ways:
  • Use the slipstream installation when running from the RTM. Specify /UPDATESOURCE parameter that points to the location with the CU package.
  • Preinstall the CU setup, and then run RTM setup to install a new instance.
  • When the CU runs on a clean box (no SQL), the CU installs the setup binaries. Then, next installation will use the patched setup.
  • When there is already SQL Server RTM installed, the CU would patch it and then next installation will use the patched setup.

References


Learn about the terminology that Microsoft uses to describe software updates.