Issue with DAML Language Server: "Could not start DAML Language Server" Error

New to Daml
1

Hello DAML Community,

I’ve encountered an issue with the DAML Language Server while working on my project. The error message I’m receiving is as follows:

[Error - 6:31:42 PM] Starting client failed
Error: spawn EINVAL
    at ChildProcess.spawn (node:internal/child_process:421:11)
    at Object.spawn (node:child_process:799:9)
    at c:\Users\Defoe\.vscode\extensions\digitalassetholdingsllc.daml-2.9.3\node_modules\vscode-languageclient\lib\node\main.js:383:40

Here’s a summary of the situation:

  • DAML Commands: daml start and daml build work as expected.
  • Issue: I get the above error when attempting to see the script results in Visual Studio Code.
  • Extension Version: Digital Asset Holdings LLC DAML Extension version 2.9.3.

I’ve tried the usual troubleshooting steps, including restarting VS Code and checking for updates, but the problem persists.

Has anyone encountered a similar issue or have any suggestions on how to resolve this? Any assistance would be greatly appreciated!

Thank you in advance!

Best regards,

2 Likes
2

This error message appears in a recent nodejs issue.

I wonder if reverting to an older version of node (e.g., Node.js v20.12.1) is a workaround. I don’t have a Windows machine handy to work out those details and test. We’re looking at this internally.

3

Same problem here.
I’m using Win10 Enterprise, nodejs 18.19.1.
I didn’t touch anything, last week was working and from yesterday I got this error (same for my team mates).
Any help? It is quite a problem for us.

Best Regards.

4

Yes, same problem for us as well

[Error - 2:11:55 PM] Starting client failed
Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at Object.spawn (node:child_process:799:9)
at c:\Users\UKe13147.vscode\extensions\digitalassetholdingsllc.daml-2.9.3\node_modules\vscode-languageclient\lib\node\main.js:383:40

DA can you please help?

5

We’re looking into this now, thanks for reporting.

1 Like
6

The issue specifically arises due to the VSCode July update bumping their NodeJS to a version that disallows the way we start the IDE. We’ll push out a fix likely for 2.9.4, but for now, you can probably get around this by using last month’s VSCode release. Please let me know if this works for you.

1 Like
7

I will wait for the fix with 2.9.4 - thank you very much