4

I was playing with the new "R" scripting in SQL Server 2016 CTP 30.
Finally got it working, thanks to this site.

I've had a problem that I'm sure others will run into as well.

All of a sudden the "R" scripts no longer worked, they returned this error:

Msg 39011, Level 16, State 1, Line 1
SQL Server was unable to communicate with the LaunchPad service. Please verify the configuration of the service.

6

In order to move TempDB to a disk with more space, I had to restart the server.
This stopped the SQL Server as well as SQL Agent, and the new "SQL Server Launchpad".

It was easy to restart SQL Server and SQL Agent.
To restart LaunchPad, I needed to go to

Administrative Tools -> Services
and find "SQL Server LaunchPad (MSSQLSERVER)"

right-click it and select "Start" and my scripts run again.

  • Does this apply to the newer versions too - SQL Server 2016 RC3? – Minu Jun 18 '16 at 23:08
  • 1
    I've checked SQL Server 2016 RTM, The SQL Server Launchpad still exist, but it is started when restarting the SQL Server. – Henrik Staun Poulsen Jun 21 '16 at 6:35
  • 1
    It is usually considered best practice to start and stop SQL Server related services using SQL Server Configuration Manager. – JediSQL May 8 at 18:21
  • @JidiSQL; it might be a good place to do so, but even the new version 18 of SSMS has an "Restart" option in Object Explorer on the server. And restarting the server should also restart all services. It didn't then (in November 2015), but it works as expected today (May 2019). – Henrik Staun Poulsen May 13 at 13:14

protected by Community May 8 at 19:34

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.