Terminal Process Terminates with Exit Code: 1 #2947
Comments
ghost
added
the
|
Thanks @VACoder looks like its likely a known start-up issue, we plan to have a preview release out for you to try in the next few days--thanks! |
|
Thanks for your patience, the new preview release is out and we think it solves this issue--when you have a chance would you mind giving it a try and letting us know? Thanks! |
SydneyhSmith
added
Needs-Repro-Info
and removed
Needs: Triage
|
Is this the 2020.9.0 ? If so I get the same thing. |
In 2020.9.0, do you get an error message in the console? If so, can you share it? |
When trying to run a hello world script:
|
|
Thanks @VACoder the logs and pop up are helpful but did anything output in the integrated console? Knowing that error message would be super helpful--thanks! |
SydneyhSmith
removed
the
Needs: Maintainer Attention
|
Nothing in the IDE other than pop ups.
<ConsoleFeature>: Unable to instantiate; language client undefined.
Loading the PowerShell extension is taking longer than expected.
If you're using privilege enforcement software, this can affect start
up performance.
Cannot debug or run a PowerShell script until the PowerShell session has
started. Wait for the PowerShell session to finish starting and try again.
…On Tue, Sep 22, 2020 at 3:49 PM Sydney Smith ***@***.***> wrote:
Thanks @VACoder <https://github.com/VACoder> the logs and pop up are
helpful but did anything output in the integrated console? Knowing that
error message would be super helpful--thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2947 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDASHWUQZ4OTRDZN7HN4G3SHEEXPANCNFSM4RIP7D7Q>
.
|
|
when writing a command into the terminal: "'write-host' is not recognized
as an internal or external command,
operable program or batch file."
…On Tue, Sep 22, 2020 at 4:18 PM Richard Ruth ***@***.***> wrote:
Nothing in the IDE other than pop ups.
<ConsoleFeature>: Unable to instantiate; language client undefined.
Loading the PowerShell extension is taking longer than expected.
If you're using privilege enforcement software, this can affect start
up performance.
Cannot debug or run a PowerShell script until the PowerShell session has
started. Wait for the PowerShell session to finish starting and try again.
On Tue, Sep 22, 2020 at 3:49 PM Sydney Smith ***@***.***>
wrote:
> Thanks @VACoder <https://github.com/VACoder> the logs and pop up are
> helpful but did anything output in the integrated console? Knowing that
> error message would be super helpful--thanks!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#2947 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABDASHWUQZ4OTRDZN7HN4G3SHEEXPANCNFSM4RIP7D7Q>
> .
>
|
|
Readding the POSH extension the following was displayed, which is, I believe, the same as the earlier one posted. |
|
So, certainly the server is not starting. It says powershell.exe started, but it isn't creating the session file. Either powershell.exe is crashing or it's simply not progressing. If it's crashing, I would expect to see red text where the Integrated Console is, either very briefly if it's a crash before the extension can handle it, or it should print the error and wait for keyboard input (so that catching startup errors is easier). If none of those things are happening, it's likely this is due to something preventing the proper progression of powershell.exe, which we've seen in almost all cases is due to anti-virus of some kind. Could you please share a GIF or video of the extension startup from start to finish so we can dig into this? |
SydneyhSmith
removed
the
Needs: Maintainer Attention
|
This issue is being closed as inactive, if this issue is still occurring it will be re-opened |
|
I'm getting the same error. Was there a fix or workaround for this? |
|
Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead. |
Issue Description
When opening vscode error is displayed immediately. Takes a long time to start then fails to load session;
There is a second message about loading powershell extension is taking longer than expected.
'Starting powerhsell' appears in the bottom bar. Clicking it shows a message:
running the contributed command: 'PowerShell.ShowSessionMenu' failed.
Eventually PowerShell session fails to start.
Attached Logs
9/11/2020 5:37:40 PM [NORMAL] - Language server starting --
9/11/2020 5:37:40 PM [NORMAL] - PowerShell executable: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
9/11/2020 5:37:40 PM [NORMAL] - PowerShell args: -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command Import-Module 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.6.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\modules' -EnableConsoleRepl -StartupBanner '' -LogLevel 'Normal' -LogPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\logs\1599863860-60081aad-8de8-4380-95ac-54cfa56310801599863859157\EditorServices.log' -SessionDetailsPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\sessions\PSES-VSCode-1708-338573' -FeatureFlags @()
9/11/2020 5:37:40 PM [NORMAL] - powershell.exe started.
9/11/2020 5:37:40 PM [NORMAL] - PowerShell Editor Services args: Import-Module 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1'; Start-EditorServices -HostName 'Visual Studio Code Host' -HostProfileId 'Microsoft.VSCode' -HostVersion '2020.6.0' -AdditionalModules @('PowerShellEditorServices.VSCode') -BundledModulesPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\modules' -EnableConsoleRepl -StartupBanner '' -LogLevel 'Normal' -LogPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\logs\1599863860-60081aad-8de8-4380-95ac-54cfa56310801599863859157\EditorServices.log' -SessionDetailsPath 'c:\Users<user>.vscode\extensions\ms-vscode.powershell-2020.6.0\sessions\PSES-VSCode-1708-338573' -FeatureFlags @()
9/11/2020 5:37:40 PM [NORMAL] - Waiting for session file
9/11/2020 5:41:41 PM [NORMAL] - Timed out waiting for session file to appear.
9/11/2020 5:41:41 PM [NORMAL] - Language server startup failed.
9/11/2020 5:41:41 PM [ERROR] - Error: Timed out waiting for session file to appear.
9/11/2020 5:41:41 PM [ERROR] - The language service could not be started:
9/11/2020 5:43:38 PM [NORMAL] - Shutting down language client...
Environment Information
Version: 1.49.0 (user setup)
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T13:22:08.892Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 6.3.9600
Visual Studio Code
PowerShell Information
Visual Studio Code Extensions
Visual Studio Code Extensions(Click to Expand)
The text was updated successfully, but these errors were encountered: