This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 50%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVH%3C/text%3E%3C/svg%3E)
Hello,
we installed a new SQL Server 2019 on a Windows Server 2019 Cluster and we are not able to get the SQL Server Launchpad Service to start. The sql server and the launchpad service are also set up as cluster ressources.
On an other non-cluster server in the same domain the launchpad service starts.
In the EXTLAUNCHERRORLOG (EXTLAUNCHERRORLOG.log) are the following errors:
2023-05-04 12:31:56.957 Security Context Manager initialization failed. ErrorCode: 0x80070002.
2023-05-04 12:31:56.959 Satellite Session Manager initialization failed. ErrorCode: 0x80070002.
2023-05-04 12:31:56.959 Initialization of satellite session manager failed. ErrorCode: 0x80070002.
In the windows application log are no entries.
In the windows security log are no audit failures.
The launchpad service is running under the account "NT Service\MSSQLLaunchpad"
This account has these privileges on both nodes via global policies
The SQLRUserGroup also has "Allow log on localy"
we also added the "NT Service\MSSQLLaunchpad" to the administrator group with no luck.
this is our Sql Server version:
Microsoft SQL Server 2019 (RTM-CU19) (KB5023049) - 15.0.4298.1 (X64) Jan 27 2023 16:44:09 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2022 Datacenter 10.0 <X64> (Build 20348: ) (Hypervisor)
this is the windows security log, when the launchpad service tries to start
and here are the pythonlauncher.log
and the rlauncher.log
I don't know much about this, but error 0x80070002 is the good ol' The system cannot find the file specified.
Possibly you could use Process Monitor to figure out what file it is looking for but cannot find.
with the help of procmon I was able to figure out that the folder
MSSQL15.MSSQLSERVER\MSSQL\ExternalLanguages
was missing.
After creating this folder, the launchpad service starts.
Thanks for the hint.
I'm delighted to hear that my feeble attempt to help was sufficient for you to find the solution! And great to hear that you got it working! Now, why that folder was missing... That's another story, I don't know the answer to.