By: Vitor Montalvao | Last Updated: 2016-11-25 | Comments (6) | SQL Server 2016
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.
Microsoft says there are at least 2 issues that can prevent the LaunchPad from starting:
- 8dot3 notation not enabled
- 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.
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.
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.
and add the local SQLRGroup to the Allow log on locally policy.
The Server Launchpad service can now be started.
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.
- More R tips
Last Updated: 2016-11-25
About the author
View all my tips