Share via

Did not find any initialized language workers

Jon Christensen 0 Reputation points
2024-02-08T14:51:51.8966667+00:00

We have an azure function that monitors a poison queue and are seeing an increase in this error message: "Did not find any initialized language workers". What does this error mean and how can we prevent it? Below is the stack trace. Running .net 7. Isolated process functions. 

Microsoft.Azure.WebJobs.Host.FunctionInvocationException:
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor+
Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,679 questions
ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,400 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. MayankBargali-MSFT 70,016 Reputation points
    2024-02-12T12:11:31.38+00:00

    @Jon Christensen Thanks for reaching out.

    Can you please confirm if you are getting this error while running your code in azure function or while testing it in your local machine?

    Looking at the error it seems like when the function invocation took place, there was not a worker available for it. This could point to a worker crash from a previous function invocation or worker initialization issue. If you are injecting any dependencies, please check if they are done properly and correct versions of SDK are being used.

    In case you are getting the error in azure function then please share more details what FUNCTIONS_WORKER_RUNTIME environment you have set in your function and default version that you have set. If you are observing the issue in local environment then please try re-installing the function core tool and see if it helps.

    0 comments