PowerShell Azure Function: How to fix "Failed to start a new language worker for runtime: powershell"?

Question

In an Azure Function App containing one PowerShell function I get the following log message regularly:

"Failed to start a new language worker for runtime: powershell."

It has "Error" level and thus triggers our error alert notifications. I'm not entirely sure when this message appears. It might appear around restarting the function app, which might explain it somewhat. I think I remember it appearing during normal function operation - but I might be mistaken.

There is a rather involved thread over here about a similar message but for the dotnet runtime that suggests there are configuration options to configure: Azure Function - Failed to start a new language worker for runtime: dotnet-isolated

My function app runtime version is ~4, PS Core version is 7.0, platform is 64 bit and Windows.

What is the error message trying to telling me? Can I ignore it? Is there a configuration I can add to fix it?

hii @heinrich Ulbricht, share more information about these problem. — PunitSharma, May 24 '22 at 08:07
@PunitSharma-MT Which information do you miss? I will add it. — Heinrich Ulbricht, May 24 '22 at 09:15
you can share code and what way use to create PowerShell function (vs or azure portal). — PunitSharma, May 24 '22 at 09:20

score 0 · Answer 1 · answered Jun 14 '22 at 08:40

After monitoring this for a while over the course of multiple deployments and restarts of PowerShell-based Function Apps my conclusion is this:

The error "Failed to start a new language worker for runtime: powershell." only appears when restarting the Function App. Thus my takeaway is that it can be ignored.

PowerShell Azure Function: How to fix "Failed to start a new language worker for runtime: powershell"?

1 Answers1