Language Server Process Didn’t Start

[aksarben]

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

I just de-installed Visual Studio Code, downloaded version 1.81.0 from https://code.visualstudio.com/download, and installed it.

When I launched , I immediately got an error message: ­

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.3.6
PSEdition                      Core
GitCommitId                    7.3.6
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visual Studio Code Version

1.81.1
6c3e3dba23e8fadc360aed75ce363ba185c49794
x64

Extension Version

[email protected]

Steps to Reproduce

Launched the program by clicking the shortcut installed on the desktop.

Visuals

Logs

The log directory specified in the instructions does not exist, and I could not locate the files. So, originally I pressed Ctrl-Shift-P and pasted the log output here. However, the output was 30 pages long, so I deleted it after I discovered the log locations and pasted links to the individual log files.

[aksarben]

Here's the actual location of the log directory (different than what the instructions said:

8/10/2023 3:33:58 PM [VERBOSE] - Creating log directory at: 'file:///c%3A/Users/Dick/AppData/Roaming/Code/User/globalStorage/ms-vscode.powershell/logs/1691699249-47432b06-ba74-40ce-ac79-707ffb8866ad1691699248564'

When I tried to run the debugger, I get these errors:

[andyleejordan]

Can you please separate those log files? I can't tell where one ends and another starts. It looks like at some point you change some setting and allow the prompt to restart the session, and after that the status says 'running' so what's the actual state after that?

[aksarben]

Hope this works. Would have done this the first time, but the instructions gave the wrong location for the log files, & I couldn't find them.

EditorServices.log
StartEditorServices.log
vscode-powershell.log

Looks like it it worked (I think). Do you need anything else?

[andyleejordan]

I don't know what email addresses you gave GitHub 😂

[aksarben]

After a lot of digging, I think I found the right place for notifications settings. Looks like you have to explicitly ask to be notified of comments on issues you’re subscribed to. Seems to defeat the purpose of subscribing. Oh well…

[aksarben]

Here's the latest screen shot from when I tried to debug this morning. Still dead in the water:

[aksarben]

I’m going through the troubleshooting page again to see if I missed anything. Re the section on Language Server Protocol Payload Logs, I’d be be happy to provide these logs if I can. The page says:

Add the following setting to your settings file: powershell editor services.trace.server:verbose"

I’m pretty new to VSC, so I’ve only dealt with settings on the settings page in the IDE. What's the name and location this "settings file"?

Also, what folder are the "payload logs" in, and what are the log files named?

[aksarben]

Tried to open the the logs folder from Ctrl-Shift-P, but got this error:

[aksarben]

Ok, finally found how to add "powershell editor services.trace.server:verbose" to my settings. Saved it and re-launched VSC, and got the usual error messages. But when I look in the log directory, none of the log files have changed since yesterday. So either I did something wrong, or the Language Server Protocol Payload Log is located somewhere else?

[starball5]

Related on Stack Overflow: Where can I find the settings file referred to in the VS Code PowerShell extension's troubleshooting page?

[aksarben]

Looks like we can call off the dogs.

When I started VSC yesterday morning, I set the log level to Diagnostic to see if could capture anything helpful in the log.

Lo, and behold, VSC ran flawlessly without a single error!

Don't have a clue why it suddenly started behaving, or what caused the problem in the first place. And, as someone wisely said, "Problems that go away by themselves tend to come back themselves." So I'm keeping my fingers crossed.

[aksarben]

Looks like we're done.

[andyleejordan]

Glad to hear it!