language server startup failed on macOS 10.14.1 (18B75)
See original GitHub issueSystem Details
VSCode version:
1.28.2 7f3ce96ff4729c91352ae6def877e59c561f4850 x64
VSCode extensions:
donjayamanne.githistory@0.4.3 ms-kubernetes-tools.vscode-kubernetes-tools@0.1.14 ms-mssql.mssql@1.4.0 ms-python.python@2018.9.2 ms-toolsai.vscode-ai@0.3.1 ms-vscode.azure-account@0.5.1 ms-vscode.cpptools@0.20.1 ms-vscode.PowerShell@1.9.0 ms-vsts.team@1.144.1 PeterJausovec.vscode-docker@0.3.1 redhat.vscode-yaml@0.1.0 vsciot-vscode.vscode-arduino@0.2.22
PSES version:
PowerShell version:
Name Value
---- -----
PSVersion 6.1.0
PSEdition Core
GitCommitId 6.1.0
OS Darwin 18.2.0 Darwin Kernel Version 18.2.0: Fri Oct 5 19:41:49 PDT 2018; root:xnu-4903.221.2~2/RELEASE_X86_64
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Issue Description
The PowerShell console in VSCode cannot start. After 2 minutes of starting it stops with the error message “The language service could not be started”.
Attached Logs
11/7/2018 3:50:39 PM [NORMAL] - Path specified by 'powerShellExePath' setting - '' - not found, reverting to default PowerShell path.
11/7/2018 3:50:42 PM [NORMAL] - Language server starting --
11/7/2018 3:50:42 PM [NORMAL] - exe: /usr/local/bin/pwsh
11/7/2018 3:50:42 PM [NORMAL] - args: /Users/Tom/.vscode/extensions/ms-vscode.powershell-1.9.0/modules/PowerShellEditorServices/Start-EditorServices.ps1 -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '1.9.0'-AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath '/Users/Tom/.vscode/extensions/ms-vscode.powershell-1.9.0/modules'-EnableConsoleRepl -LogLevel 'Normal' -LogPath '/Users/Tom/.vscode/extensions/ms-vscode.powershell-1.9.0/logs/1541602239-f4c34257-a983-41bb-a211-d260bd964adb1541602224073/EditorServices.log' -SessionDetailsPath '/Users/Tom/.vscode/extensions/ms-vscode.powershell-1.9.0/sessions/PSES-VSCode-10449-748238' -FeatureFlags @()
11/7/2018 3:50:43 PM [NORMAL] - Syntax Folding Provider registered
11/7/2018 3:52:43 PM [NORMAL] - Language server startup failed.
11/7/2018 3:52:43 PM [ERROR] - The language service could not be started:
11/7/2018 3:52:43 PM [ERROR] - Timed out waiting for session file to appear.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Fixing Visual Studio Code Failed to Run PowerShell Scripts
After a Visual Studio Code update the other day, all the PowerShell scripts refusing to run due to a "Language server startup failed"....
Read more >SSH failure after update to Mojave 10.14.1 - Apple Community
I used SSH to connect to remote servers. My OS was the SIERRA. After upgrading to MOjave 10.14.1 (18B75) the connections stopped working....
Read more >Quadro & GeForce macOS Driver Release 387.10.10.10.40.105
Version: 387.10.10.10.40.105 ; Release Date: 2018.7.10 ; Operating System: macOS High Sierra 10.13.6 ; CUDA Toolkit: 9.1. Language ; Language: English (US).
Read more >Unable to start the Python language server - Stack Overflow
Error : WARNING: The script pyls is installed in '/Users/baner75418/Library/Python/2.7/bin' which is not on PATH. Consider ...
Read more >Apple Releases macOS 10.14.1 With Group FaceTime and ...
Apple today released macOS Mojave 10.14.1, the first major update to the macOS Mojave operating system available on Apple's Mac lineup.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
After purging all elements and re-installation VSCode and the PS extension everything seems to work, again. Not sure what it was but for now I’m fine.
Thank you for your effort.
Yep that’s the command — missed a word there.
It looks our usual options aren’t available then.
If that’s the only file in the logs folder then the failure is probably pretty early and there’s a good chance it’s in
Start-EditorServices.ps1
.Try putting a
Wait-Debugger
in there and tracing through.