In the future you can check the status of the role out using the link below:
https://aspnetcoreon.azurewebsites.net/#
.NET Core 3.1 not recognized by Web Job
I have a Web API and Web Job running .NET Core 3.1. While the Web API is running fine the Web Job will not start. When I went into the logs I discovered that it cannot find the .NET Core 3.1 runtime. You'll notice here that I do actually have the runtime extension installed.
But as you'll notice here in the logs, it cannot see the runtime. I have restarted the Web App more than a few times, and had to do it once just to get the Web API to pick it up. Even leaving it over night and restarting the Web Job still cannot find the runtime.
[12/06/2019 14:36:42 > 4e52af: SYS INFO] Run script 'MyProject.Worker.exe' with script host - 'WindowsScriptHost'
[12/06/2019 14:36:42 > 4e52af: SYS INFO] Status changed to Running
[12/06/2019 14:36:42 > 4e52af: ERR ] It was not possible to find any compatible framework version
[12/06/2019 14:36:42 > 4e52af: ERR ] The specified framework 'Microsoft.NETCore.App', version '3.1.0' was not found.
[12/06/2019 14:36:42 > 4e52af: ERR ] - The following frameworks were found:
[12/06/2019 14:36:42 > 4e52af: ERR ] 2.2.7 at [D:\Program Files\dotnet\shared\Microsoft.NETCore.App]
[12/06/2019 14:36:42 > 4e52af: ERR ] 3.0.0 at [D:\Program Files\dotnet\shared\Microsoft.NETCore.App]
[12/06/2019 14:36:42 > 4e52af: ERR ]
[12/06/2019 14:36:42 > 4e52af: ERR ] You can resolve the problem by installing the specified framework and/or SDK.
[12/06/2019 14:36:42 > 4e52af: ERR ]
[12/06/2019 14:36:42 > 4e52af: ERR ] The .NET Core frameworks can be found at:
[12/06/2019 14:36:42 > 4e52af: ERR ] - https://aka.ms/dotnet-download
[12/06/2019 14:36:42 > 4e52af: SYS ERR ] Job failed due to exit code -2147450730
[12/06/2019 14:36:42 > 4e52af: SYS INFO] Process went down, waiting for 60 seconds
[12/06/2019 14:36:42 > 4e52af: SYS INFO] Status changed to PendingRestart
2 answers
Sort by: Most helpful
-
Jeremy Brooks 572 Reputation points Microsoft Employee
2020-01-09T15:12:36.77+00:00 -
Wouter 1 Reputation point
2020-01-15T08:12:46.797+00:00 I resolved the issue by disabling the "Set .NET Core version to 3.1.100" task in azure devops.