Skip to content

[Erreur] Could not start language service: undefined #252

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
theyanster opened this issue Aug 22, 2016 · 2 comments
Closed

[Erreur] Could not start language service: undefined #252

theyanster opened this issue Aug 22, 2016 · 2 comments

Comments

@theyanster
Copy link

Extension version: 0.7.0
Visual Code version: 1.4.0
OS: Windows 7 Pro SP1 x64, French
PowerShell version installed on system (output of $PSVersionTable):

Name                           Value
----                           -----
PSVersion                      3.0
WSManStackVersion              3.0
SerializationVersion           1.1.0.1
CLRVersion                     4.0.30319.34209
BuildVersion                   6.2.9200.16398
PSCompatibleVersions           {1.0, 2.0, 3.0}
PSRemotingProtocolVersion      2.2

Description:

Getting following errors when opening a PowerShell script after installing the PowerShell extension:

[Erreur] Could not start language service: undefined
[Erreur] Couldn't start client PowerShell Editor Services

(Note: the word Erreur is not a typo, it's in French)

Steps to reproduce:

  1. Install the PowerShell extension
  2. Activate it
  3. Once the interface reloads, open any PowerShell script

I'm not sure if this could be an issue with the fact my OS is in French, but it could be as I didn't have the issue on other English versions of Windows and even Ubuntu 16.04.

@theyanster
Copy link
Author

2016-08-22_11-16-54

@theyanster theyanster changed the title Extension fails to load when opening PowerShell script [Erreur] Could not start language service: undefined Aug 22, 2016
@daviwil
Copy link
Contributor

daviwil commented Aug 22, 2016

Hey @theyanster, this is definitely an issue with the extension running on PS 3.0. I'm going to try to get a fix out for this today or tomorrow. You can check out the following issue for more details and a temporary workaround:

#248

I'll close this issue since we're already tracking it over at #248. Thanks for the report!

@daviwil daviwil closed this as completed Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants