SQL Server 2019 LaunchPad Service won't start

Question

SQL Server 2019 LaunchPad Service won't start

Peter Bishop 181

I have added R and Python to a SQL Server 2019 Developer Edition instance and patched to CU23. However the service won't start. There are no errors reported in the Event Viewer (other than "service start timeout") and there is nothing at all in the ExtensibilityLog.

The R User group has all the permissions I've found in other forum posts but I'm not having any luck.

Can anyone advise, even if it's just to get some errors to investigate? Thanks.

Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-09T19:15:43.73+00:00

What is the service account for the launchpad service?

One alternative for troubleshooting would be to try to start the program from a command-line window, taking the command-line from the Services applet.

Is this on your private machine or in a corporate environment?
Peter Bishop 181 Reputation points

2023-12-09T21:25:15.35+00:00

Service account = NT Service\MSSQLLaunchpad$instancename

Small home domain, though unsure what difference that would make?
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-09T22:21:27.51+00:00

That's the normal service account. I was asking about the environment, since in a corporate environment there could be policies that prevent the service from starting. Less likely at home, I guess.

Did you try to run the executable directly? That would be with different credentials, so the result may not be the same. But you could at least try.
Peter Bishop 181 Reputation points

2023-12-09T23:41:58.7033333+00:00

Sorry, forgot that part. Managed to extract the executable using WMI, giving quite possibly the longest command line I've ever seen!

For info, in PowerShell I executed:

Get-WmiObject win32_service | Where-Object {$_.DisplayName -like 'SQL Server Launchpad*'} | Select-Object PathName | Format-Table -Wrap

Running this under my own account I got the following:

2023-12-10 10:18:54.471 Page exclusion bitmap is enabled.
2023-12-10 10:18:54.611 StartServiceDispatcherTask Completed. ErrorCode: 0x00000000
2023-12-10 10:18:54.611 ServiceDispatcherTask Failed. ErrorCode: 0x80070427
2023-12-10 10:18:54.611 Privilege SeAssignPrimaryTokenPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Privilege SeChangeNotifyPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Privilege SeIncreaseQuotaPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Launchpad process is NOT a part of Service Group. Launchpad does NOT have SeServiceLogonRight.
2023-12-10 10:18:54.611 SetNecessaryPrivileges failed. ErrorCode: 0x80040004.
2023-12-10 10:18:54.627 A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 41544, committed (KB): 81872, memory utilization: 50
2023-12-10 10:19:35.100 Running ControlHandler, calling with control signal type: 0

I can understand these errors, since my account doesn't have those rights. However I've cheked the service account and these have all be provisioned.

Strangely trying to start the service again, after running this command, worked. I have no idea why but thanks for the pointer.
Peter Bishop 181 Reputation points

2023-12-09T23:49:10.8233333+00:00

Note that I did also check the permissions on the "ExternalLanguagesTemp" and "ExternalLibrariesTemp" folders which resulted in the message:

You must had Read permissions to view the properties of this object

After clicking on "Advanced" I could confirm that the service account had Full Control to these folders.
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-10T11:00:36.0033333+00:00

So it works now, although we don't know why, and we don't why it did not work before?
Peter Bishop 181 Reputation points

2023-12-10T14:42:31.6066667+00:00

That's exactly correct.

1 answer

Your answer

Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-09T19:15:43.73+00:00

What is the service account for the launchpad service?

One alternative for troubleshooting would be to try to start the program from a command-line window, taking the command-line from the Services applet.

Is this on your private machine or in a corporate environment?
Peter Bishop 181 Reputation points

2023-12-09T21:25:15.35+00:00

Service account = NT Service\MSSQLLaunchpad$instancename

Small home domain, though unsure what difference that would make?
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-09T22:21:27.51+00:00

That's the normal service account. I was asking about the environment, since in a corporate environment there could be policies that prevent the service from starting. Less likely at home, I guess.

Did you try to run the executable directly? That would be with different credentials, so the result may not be the same. But you could at least try.
Peter Bishop 181 Reputation points

2023-12-09T23:41:58.7033333+00:00

Sorry, forgot that part. Managed to extract the executable using WMI, giving quite possibly the longest command line I've ever seen!

For info, in PowerShell I executed:

Get-WmiObject win32_service | Where-Object {$_.DisplayName -like 'SQL Server Launchpad*'} | Select-Object PathName | Format-Table -Wrap

Running this under my own account I got the following:

2023-12-10 10:18:54.471 Page exclusion bitmap is enabled.
2023-12-10 10:18:54.611 StartServiceDispatcherTask Completed. ErrorCode: 0x00000000
2023-12-10 10:18:54.611 ServiceDispatcherTask Failed. ErrorCode: 0x80070427
2023-12-10 10:18:54.611 Privilege SeAssignPrimaryTokenPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Privilege SeChangeNotifyPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Privilege SeIncreaseQuotaPrivilege is not present in launchpad process token.
2023-12-10 10:18:54.611 Launchpad process is NOT a part of Service Group. Launchpad does NOT have SeServiceLogonRight.
2023-12-10 10:18:54.611 SetNecessaryPrivileges failed. ErrorCode: 0x80040004.
2023-12-10 10:18:54.627 A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 41544, committed (KB): 81872, memory utilization: 50
2023-12-10 10:19:35.100 Running ControlHandler, calling with control signal type: 0

I can understand these errors, since my account doesn't have those rights. However I've cheked the service account and these have all be provisioned.

Strangely trying to start the service again, after running this command, worked. I have no idea why but thanks for the pointer.
Peter Bishop 181 Reputation points

2023-12-09T23:49:10.8233333+00:00

Note that I did also check the permissions on the "ExternalLanguagesTemp" and "ExternalLibrariesTemp" folders which resulted in the message:

You must had Read permissions to view the properties of this object

After clicking on "Advanced" I could confirm that the service account had Full Control to these folders.
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-10T11:00:36.0033333+00:00

So it works now, although we don't know why, and we don't why it did not work before?
Peter Bishop 181 Reputation points

2023-12-10T14:42:31.6066667+00:00

That's exactly correct.

Answer 1

It seems like the R and Python services on your SQL Server 2019 Developer Edition instance are facing startup issues. Here are some steps you can take to troubleshoot:

Check SQL Server Error Log:

Examine the SQL Server Error Log for any specific error messages related to the R and Python services. This log can provide detailed information about the issues.

Check SQL Server Configuration Manager:

Ensure that the R and Python services are enabled and set to start automatically in the SQL Server Configuration Manager.

Permissions:

Verify that the service accounts for R and Python have the necessary permissions to access resources and execute.

Service Account Permissions:

Ensure that the service account running SQL Server has the required permissions for R and Python integration.

Firewall Settings:

Confirm that firewall settings are not blocking the communication for R and Python services.

Service Timeout:

Increase the service start timeout duration in case the default timeout is too short.

Event Viewer:

Check the Windows Event Viewer for any system-level issues that might be affecting the startup of services.

Service Dependency:

Ensure that there are no dependencies missing for the R and Python services.

If you can provide more specific error messages or details from the SQL Server Error Log, it would be helpful in diagnosing the problem.

Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2023-12-10T16:37:44.5433333+00:00

Don't you have a feeling that you are coming late to the party? The issue appears to be resolved.

Also, I kind of get the impression that this is something that comes from Chat GPT or a similar service. If that is indeed the case, you post is in violation with the AI usage policy for Microsoft Q&A. The policy permits you use output from AI services in your answers, but it is a requirement that you make it clear in your post that you used an AI service, and which service you used. You are also expected to verify the answer - we all know that Chat GPT is able to quite a bit of imagination, and cannot always be trusted. I recommend that you study the policy. Continued violations of the policy can lead to suspension of your account.

Share via

SQL Server 2019 LaunchPad Service won't start

1 answer

Your answer