FIX: SQL Server Launchpad service fails to start if the installed version of R Services (In-Database) is different from the Database Engine in SQL Server 2016

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core

Symptoms


If you install R Services (In-Database) separately from the Database Engine in Microsoft SQL Server 2016 and if their versions are different, the SQL Server Launchpad service may fail to start. Additionally, error messages that resemble the following are logged in the SQL Server error log:

A timeout was reached (30000 milliseconds) while waiting for the SQL Server Launchpad (BI_DW) service to connect.

The SQL Server Launchpad (BI_DW) service failed to start due to the following error:  The service did not respond to the start or control request in a timely fashion.

 

Resolution


This issue is fixed in the following cumulative updates for SQL Server:

       Cumulative Update 5 for SQL Server 2016 RTM

       Cumulative Update 2 for SQL Server 2016 SP1

 

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


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