DurableFunctionsMonitor: Backend fails to start
Trying to start the backend in VSCODE, I can see the following log:
Azure Functions Core Tools
Core Tools Version: 4.0.4785 Commit hash: N/A (64-bit)
Function Runtime Version: 4.10.4.19213
Warning: Proxies are not supported in Azure Functions v4. Instead of 'proxies.json', try Azure API Management: https://aka.ms/AAfiueq
[2022-11-25T15:58:10.623Z] Csproj not found in c:\Users\junior\.vscode\extensions\durablefunctionsmonitor.durablefunctionsmonitor-6.0.0\backend directory tree. Skipping user secrets file configuration.
[2022-11-25T15:58:17.990Z] A host error has occurred during startup operation '4bac7748-7552-499c-aa98-c04bfd6e38b8'.
[2022-11-25T15:58:17.990Z] Microsoft.Azure.WebJobs.Extensions.Http: Could not load file or assembly 'System.Net.Http.Formatting, Version=5.2.8.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
ERROR: Value cannot be null. (Parameter 'provider')ERROR:
It does not complete.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (8 by maintainers)
I was facing the same issue reported by @junalmeida. Removing and installing the latest version of Azure Functions Core Tools (version 4.0.4915) fixed the issue.
I also updated tooling and it works like @xsurfer pointed out.
I actually solved this. It was using my azure-functions-core-tools from this folder: /Users/*****/.nvm/versions/node/v16.15.0/lib/node_modules/azure-functions-core-tools/bin/func which was v.4.0.4544 So I changed the extension setting durableFunctionsMonitor.customPathToAzureFunctionsHost to point to /usr/local/bin/func which is 4.0.4915 and it started work all ok.
I already updated my nvm default node version so its not what it was before.
Well I have very same issue. When I set explicitly what @scale-tone proposed here:
it all works well, finds and loads 17 functions and job host starts ok. BUT when I try to open DFM from VCS I get this
@mpriem does it work for you now when triggered from VCS?
sorry. I see what is wrong here. I’m using the VSCode extension and it tries to run it inside the same workspace as my PowerShell functions project. I now moved it inside a dotnet based container and the backend starts without issues.
Thanks for getting me on the right path @scale-tone