Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Failed to start Language Worker Channel for language PowerShell
See original GitHub issueGet-History output:
Id CommandLine
-- ----------- 1 npm i -g azure-functions-core-tools --unsafe-perm true 2 func
3 cd C:\temp\
4 func init --worker-runtime powershell
5 cd .\MyFunctionProj\
6 ls
7 func new -l powershell -t HttpTrigger -n DemoTrigger
8 func start
When the function starts, the following error is logged:
A host error has occurred
Microsoft.Azure.WebJobs.Script: Failed to start Language Worker Channel for language :powershell. System.Diagnostics.Process: The system cannot find the file specified.
Full log until the error occurs:
Azure Functions Core Tools (2.7.1373 Commit hash: cd9bfca26f9c7fe06ce245f5bf69bc6486a685dd) Function Runtime Version: 2.0.12507.0 [22.06.2019 14:03:42] Starting Rpc Initialization Service. [22.06.2019 14:03:42] Initializing RpcServer [22.06.2019 14:03:42] Building host: startup suppressed:False, configuration suppressed: False [22.06.2019 14:03:42] Initializing Host. [22.06.2019 14:03:42] Host initialization: ConsecutiveErrors=0, StartupCount=1 [22.06.2019 14:03:42] LoggerFilterOptions [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "MinLevel": "None", [22.06.2019 14:03:42] "Rules": [ [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "ProviderName": null, [22.06.2019 14:03:42] "CategoryName": null, [22.06.2019 14:03:42] "LogLevel": null, [22.06.2019 14:03:42] "Filter": "<AddFilter>b__0" [22.06.2019 14:03:42] }, [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", [22.06.2019 14:03:42] "CategoryName": null, [22.06.2019 14:03:42] "LogLevel": "None", [22.06.2019 14:03:42] "Filter": null [22.06.2019 14:03:42] }, [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "ProviderName": "Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.SystemLoggerProvider", [22.06.2019 14:03:42] "CategoryName": null, [22.06.2019 14:03:42] "LogLevel": null, [22.06.2019 14:03:42] "Filter": "<AddFilter>b__0" [22.06.2019 14:03:42] } [22.06.2019 14:03:42] ] [22.06.2019 14:03:42] } [22.06.2019 14:03:42] FunctionResultAggregatorOptions [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "BatchSize": 1000,
[22.06.2019 14:03:42] "FlushTimeout": "00:00:30", [22.06.2019 14:03:42] "IsEnabled": true [22.06.2019 14:03:42] } [22.06.2019 14:03:42] SingletonOptions [22.06.2019 14:03:42] { [22.06.2019 14:03:42] "LockPeriod": "00:00:15", [22.06.2019 14:03:42] "ListenerLockPeriod": "00:00:15", [22.06.2019 14:03:42] "LockAcquisitionTimeout": "10675199.02:48:05.4775807", [22.06.2019 14:03:42] "LockAcquisitionPollingInterval": "00:00:05",
[22.06.2019 14:03:42] "ListenerLockRecoveryPollingInterval": "00:01:00" [22.06.2019 14:03:42] }
[22.06.2019 14:03:42] Starting JobHost [22.06.2019 14:03:42] Starting Host (HostId=noosljanring3-1294108133, InstanceId=88a69af8-8c4b-4050-8b05-00b4e2ed15b3, Version=2.0.12507.0, ProcessId=11268, AppDomainId=1, InDebugMode=False, InDiagnosticMode=False, FunctionsExtensionVersion=)
[22.06.2019 14:03:42] Loading functions metadata
[22.06.2019 14:03:42] 1 functions loaded
[22.06.2019 14:03:42] Starting language worker process:dotnet "C:\Users\janring\AppData\Roaming\npm\node_modules\azure-functions-core-tools\bin\workers\powershell\Microsoft.Azure.Functions.PowerShellWorker.dll" --host 127.0.0.1 --port 57975 --workerId 48cfefdb-6480-4b1f-b6b2-5891ad26ddf5 --requestId 2a3d0801-ab32-4204-b543-ab980549facd --grpcMaxMessageLength 134217728
[22.06.2019 14:03:42] A host error has occurred
**[22.06.2019 14:03:42] Microsoft.Azure.WebJobs.Script: Failed to start Language Worker Channel for language :powershell. System.Diagnostics.Process: The system cannot find the file specified.** [22.06.2019 14:03:42] Stopping JobHost
[22.06.2019 14:03:42] Building host: startup suppressed:True, configuration suppressed: False [22.06.2019 14:03:43] Initializing Host.
[22.06.2019 14:03:43] Host initialization: ConsecutiveErrors=1, StartupCount=2
$PSVersionTable:
Name Value
---- -----
PSVersion 6.2.1
PSEdition Core
GitCommitId 6.2.1
OS Microsoft Windows 10.0.18362
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Failed to start a new language worker for runtime: dotnet ...
I have a dotnet 5 function app that I've been building and deploying from a devops pipeline for a couple of weeks. Following...
Read more >I have an error (Failed to start a new language worker for ...
I have an error (Failed to start a new language worker for runtime: dotnet-isolated) after deploying the isolated Azure Function developed ...
Read more >Getting "Failed to start a new language worker for runtime ...
We have deployed a durable function to the Function App service and are getting the following error in the log when we run...
Read more >Azure Function - Failed to start a new language worker for ...
I have a dotnet 5 function app that I've been building and deploying from a devops pipeline for a couple of weeks. Following...
Read more >Azure Functions “Failed to start language worker process for
To fix this, you need to set your function app to use Node 8.11.1. Here is how. Go to your function app, and...
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
@TylerLeonhardt: I agree that we should add a check. However, this validation should take place in the Core Tools. I have opened an issue to address this. For more info, please see https://github.com/Azure/azure-functions-core-tools/issues/1410
Ah - that was it, thanks. I just got a new laptop and haven’t installed .NET Core SDK, which obviously was installed on the previous one where the function was working locally.
Would it be possible to add a prerequisite check to make it easier for the user to realize what is missing?