Learn more about SQL Server tools

mssqltips logo
 

Tutorials          DBA          Dev          BI          Career          Categories          Webcasts          Whitepapers          Today's Tip          Join

Tutorials      DBA      Dev      BI      Categories      Webcasts

DBA    Dev    BI    Categories

 

SQL Server Launchpad service cannot be started


By:   |   Read Comments   |   Related Tips: More > SQL Server 2016

Quickly Resolve Performance Problems for IIS, .NET and SQL Server       >>>   Get Started


Problem

When you try to start the SQL Server Launchpad service you get the following error: The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable logs for details.

The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable logs for details.
Solution

Microsoft says there are at least 2 issues that can prevent the LaunchPad from starting:

  1. 8dot3 notation not enabled
  2. The account that runs Launchpad has been changed or necessary permissions have been removed

To check this issue, I noticed the drive where R Services was installed supported the creation of short file names using the 8dot3 notation and I also validated that the default SQL Server Launchpad account had the necessary policies set as follows:

  • Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
  • Bypass traverse checking (SeChangeNotifyPrivilege)
  • Log on as a service (SeServiceLogonRight)
  • Replace a process-level token (SeAssignPrimaryTokenPrivilege)

So what we are trying to resolve in this tip is a third issue that Microsoft didn't explain in their article.

Troubleshooting the SQL Server Launchpad service Issue

Analyzing the Event Viewer we can see that a Security event ID 4625 has been logged.

Analyzing the Event Viewer we can see that a Security event ID 4625 has been logged.

That event says that the MSSQLSERVER01 account has not been granted local logon access. 

What is the MSSQLSERVER01 account?

When R Services is installed, 20 local users (MSSQLSERVERnn) are created in the server and one local group named SQLRUserGroup is also created with the 20 new local users added as group members.

Members of the SQLRUserGroup

With this we've found the third issue for the Launchpad service not being to start: lack of permissions for SQLRUserGroup.

Let's solve it by opening the Local Security Policy tool.

Local Security Policy

and add the local SQLRGroup to the Allow log on locally policy.

add the local SQLRGroup to the Allow log on locally policy

The Server Launchpad service can now be started.

SQL Server Configuration Manager showing the SQL Server Launchpad service is started
Conclusion

Sometimes Microsoft documentation might miss some information and in cases like this when a new feature is released, there is very little information on the Internet for troubleshooting. When that happens always check the Event and Error logs since there is usually important information that can lead you to understand and resolve the issue.

Next Steps


Last Update:


signup button

next tip button



About the author
MSSQLTips author Vitor Montalvao Vitor Montalv„o is a SQL Server engineer with 20 years of experience in SQL Server, specializing in performance & tuning, data modelling, migration and security.

View all my tips
Related Resources





Post a comment or let the author know this tip helped.

All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (*).

*Name    *Email    Notify for updates 


SQL tips:

*Enter Code refresh code     



Learn more about SQL Server tools