The Language Service could not be started.

[RumRogerz]

2018-6-11 11:31:48 [NORMAL] - Visual Studio Code v1.24.0 64-bit
2018-6-11 11:31:48 [NORMAL] - PowerShell Extension v1.7.0
2018-6-11 11:31:48 [NORMAL] - Operating System: Windows 64-bit
2018-6-11 11:31:48 [NORMAL] - Path specified by 'powerShellExePath' setting - '' - not found, reverting to default PowerShell path.
2018-6-11 11:31:48 [NORMAL] - Language server starting --
2018-6-11 11:31:48 [NORMAL] -     exe: C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
2018-6-11 11:31:48 [NORMAL] -     args: C:\Users\rdattilo\.vscode\extensions\ms-vscode.powershell-1.7.0\modules\PowerShellEditorServices\Start-EditorServices.ps1 -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '1.7.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'C:\Users\rdattilo\.vscode\extensions\ms-vscode.powershell-1.7.0\modules' -EnableConsoleRepl -LogLevel 'Verbose' -LogPath 'C:\Users\rdattilo\.vscode\extensions\ms-vscode.powershell-1.7.0\logs\1528731108-8debbaed-db66-4139-b259-39746061c6391528731105860\EditorServices.log' -SessionDetailsPath 'C:\Users\rdattilo\.vscode\extensions\ms-vscode.powershell-1.7.0\sessions\PSES-VSCode-17688-512792' -FeatureFlags @()
2018-6-11 11:31:49 [NORMAL] - powershell.exe started, pid: 19508
2018-6-11 11:32:48 [NORMAL] - Language server startup failed.
2018-6-11 11:32:48 [ERROR] - The language service could not be started: 
2018-6-11 11:32:48 [ERROR] - Timed out waiting for session file to appear.

This is all of the sudden started happening. It was fine a few days ago and then,this :(

I've uninstalled VsCode, uninstalled the powershell add-in..... several times.

Name                           Value
----                           -----
PSVersion                      5.1.17134.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17134.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1`

thats my PS version I'm running. The only thing of late that has changed on my PC is an update to Windows 1803. Although I was using VSCode just fine after the update. Maybe there is some sort of weird connection to this?

[TylerLeonhardt]

Thanks for this. Can you attach the logs so we can help further?

https://github.com/PowerShell/vscode-powershell/blob/master/README.md#2-capture-verbose-logs-and-send-them-to-us

In your case, please set the log level to Diagnostic.

[RumRogerz]

1528734640-e5c19306-07b0-4eb7-954a-fdf2563bffaf1528734636488.zip

Oddly enough, It's set to diagnostic, but it's still pumping out the exact same information. I thought there would be more.

I DO get this when I try to open a ps1 file in the terminal section:

Transcript started, output file is C:\Users\rdattilo.vscode\extensions\ms-vscode.powershell-1.7.0\logs\1528734640-e5c19306-07b0-4eb7-954a-fdf2563bffaf1528734636488\Start-EditorServices.log
VERBOSE:
#-- Updated PSModulePath to: -------------------------------------------------
VERBOSE: C:\Users\rdattilo\Documents\WindowsPowerShell\Modules
VERBOSE: C:\Program Files\WindowsPowerShell\Modules
VERBOSE: C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
VERBOSE: C:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules
VERBOSE: C:\Program Files\Common Files\Skype for Business Online\Modules
VERBOSE: C:\Users\rdattilo.vscode\extensions\ms-vscode.powershell-1.7.0\modules
VERBOSE:
#-- Check required modules available -----------------------------------------
VERBOSE: Testing module availability PowerShellGet
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1'.
VERBOSE: PowerShellGet found
VERBOSE:
#-- Start up PowerShellEditorServices ----------------------------------------
VERBOSE: Importing PowerShellEditorServices
VERBOSE: Loading module from path 'C:\Users\rdattilo.vscode\extensions\ms-vscode.powershell-1.7.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'.
VERBOSE: Loading module from path 'C:\Users\rdattilo.vscode\extensions\ms-vscode.powershell-1.7.0\modules\PowerShellEditorServices\PowerShellEditorServices.psm1'.
VERBOSE: Exporting function 'Start-EditorServicesHost'.
VERBOSE: Exporting function 'Compress-LogDir'.
VERBOSE: Exporting function 'Get-PowerShellEditorServicesVersion'.
VERBOSE: Importing function 'Compress-LogDir'.
VERBOSE: Importing function 'Get-PowerShellEditorServicesVersion'.
VERBOSE: Importing function 'Start-EditorServicesHost'.
VERBOSE: Checking port: 28572, attempts remaining 10 --------------------
VERBOSE: Testing availability of port 28572 at address 127.0.0.1 / InterNetwork
VERBOSE: Port: 28572 is available
VERBOSE: Checking port: 19180, attempts remaining 10 --------------------
VERBOSE: Testing availability of port 19180 at address 127.0.0.1 / InterNetwork
VERBOSE: Port: 19180 is available
PowerShell Integrated Console

VERBOSE:

Invoking Start-EditorServicesHost
VERBOSE: Start-EditorServicesHost returned Microsoft.PowerShell.EditorServices.Host.EditorServicesHost
VERBOSE: Writing session file with contents:
VERBOSE: {"debugServicePort":19180,"status":"started","debugServiceTransport":"Tcp","languageServiceTransport":"Tcp","languageServicePort":28572}
VERBOSE: Wrote out session file
VERBOSE:
#-- Waiting for EditorServicesHost to complete execution ---------------------

But that Editor Services log file doesn't even exist!

[TylerLeonhardt]

Do you have any sort of restrictions on your PC, @RumRogerz?

I want to rule out the possibility of the vscode extension not being able to create the session file because of permissions.

[RumRogerz]

Great question, but no. I am the commander and ruler of all the things on my pc.
Even killed off my AV for a round of troubleshooting to see if it was perhaps the culprit.... to no avail. :(

@RumRogerz
#1048 (comment)

[TylerLeonhardt]

@Wand3rvogel can you explain with some detail on how you called this function?

[rjmholt]

Looks like here:

vscode-powershell/src/utils.ts

Line 89 in 9b511a5

innerTryFunc(60, 1000);

@tylerl0706 i've found this here:
a86354d
from
#562

[TylerLeonhardt]

Ah so you're saying we should up the timeout... I think that's probably reasonable to set it to 120 seconds. Thought?

[RumRogerz]

well, it couldn’t hurt. Ima try this out and report back

[rjmholt]

This isn't necessarily a good suggestion, but... we could always make it a user-configurable extension setting...

[rjmholt]

@RumRogerz Did you get any results playing with the timeout value? In any case, we might just up the default timeout value.

[RumRogerz]

@rjmholt
Sorry about the lateness of my reply, but yes! I played around with the default value to 120 seconds and that totally solved all my woes. Now I'm shelling with power.

You can consider this ticket closed