Migrated our previously working Azure Function from Isolated Net 7 to Isolated Net 8 (RC1) and it now fails with "Server Error. There was an unexpected error in the request processing." Diagnose and solve problems shows the following critical error Function runs fine in local dev environment. Tried deleting the function, deleting the publish profile, then created a new publish profile with VBS 2022 Preview 2, but got the same problem. nb. Hosted in Australia South East

@Lindsay Mathieson We appreciate your patience on this. Our Product Group team has confirmed that the fix has been published and this issue has been resolved for Python 3.11 and .NET Isolated 8. Please confirm if you still encounter the same issue. We sincerely apologize for any inconvenience caused due to this. ** Please ' Accept as answer ' and ‘ Upvote ’ if it helped so that it can help others in the community looking for help on similar topics.

How to solve DOTNET-ISOLATED|8.0 has been deprecated as a language for Azure Functions

Lindsay Mathieson 35

Migrated our previously working Azure Function from Isolated Net 7 to Isolated Net 8 (RC1) and it now fails with "Server Error. There was an unexpected error in the request processing."

Diagnose and solve problems shows the following critical error

User's image

Function runs fine in local dev environment.

Tried deleting the function, deleting the publish profile, then created a new publish profile with VBS 2022 Preview 2, but got the same problem.

nb. Hosted in Australia South East

navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-22T06:16:08.4466667+00:00
@Lindsay Mathieson Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

I understand that your concern is related to the error DOTNET-ISOLATED|8.0 has been deprecated as a language for Azure Functions.

For function apps running on Linux, linuxFxVersion indicates the language and version for the language-specific worker process. This information is used, along with FUNCTIONS_EXTENSION_VERSION, to determine which specific Linux container image is installed to run your function app. This value is set for you when you create your Linux function app.

You can run the below Azure CLI command to see a table of current linuxFxVersion values, by supported Functions runtime version:

az functionapp list-runtimes --os linux --query "[].{stack:join(' ', [runtime, version]), LinuxFxVersion:linux_fx_version, SupportedFunctionsVersions:to_string(supported_functions_versions[])}" --output table

Use the following Azure CLI commands to view and set the linuxFxVersion. You can't currently set linuxFxVersion in the portal or by using Azure PowerShell.

To view the current runtime version, use the below AzCLI command:

az functionapp config show --name <function_app> \ --resource-group <my_resource_group> --query 'linuxFxVersion' -o tsv

To update the linuxFxVersion setting in the function app, use the following AzCLICommand:

az functionapp config set --name <FUNCTION_APP> \ --resource-group <RESOURCE_GROUP> \ --linux-fx-version DOTNET-ISOLATED|8.0

Also please check and let mw know what is the FUNCTIONS_EXTENSION_VERSION being used in your Azure Function App settings ?

Sharing some useful articles: https://learn.microsoft.com/en-us/azure/azure-functions/functions-app-settings#functions_extension_version https://learn.microsoft.com/en-us/azure/azure-functions/set-runtime-version?tabs=portal

Also in the meantime, I am checking this internally at my end to check if this issue has been reported by our other customers. I will keep you posted about this.
Lindsay Mathieson 35 Reputation points

2023-09-22T06:34:55.89+00:00
Thanks for the quick reply!

Using my function name and resource group, I ran "az functionapp config show ..." and it returned just the one line

linuxFxVersion

With nothing else. I ran

az functionapp config set --name <FUNCTION_APP> --resource-group <RESOURCE_GROUP> --linux-fx-version "DOTNET-ISOLATED|8.0:

With no errors, it returned a json object with various properties, including "linuxFxVersion": "DOTNET-ISOLATED|8.0".

FUNCTIONS_EXTENSION_VERSION is "~4"
navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-22T06:44:06.6533333+00:00

@Lindsay Mathieson Thanks for getting back. Could you please confirm even after setting the right "linuxFxVersion": "DOTNET-ISOLATED|8.0" you are still facing the same issue ? Awaiting your reply.
Lindsay Mathieson 35 Reputation points

2023-09-22T06:59:01.4333333+00:00

Yes, sorry, same issue.

nb. Also, after setting "linuxFxVersion": "DOTNET-ISOLATED|8.0", "az functionapp config show ..." still just returns "linuxFxVersion" (no value for it).
navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-22T07:01:49.0633333+00:00

@Lindsay Mathieson Thanks for the update. I have checked this internally and seems like we have a couple of issues reported for the same issue. I am working internally with the Product Group team and I will keep you posted about the progress. We appreciate your patience on this.
Lindsay Mathieson 35 Reputation points

2023-09-22T07:09:21.48+00:00

Thanks, appreciate the update. This isn't critical for us, still in dev and can always revert to dotnet 7. Happy to do any other test you need or make debug info available.

nb. The diagnostics genie lists this exception on startup.
navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-25T03:57:53.0833333+00:00

@Lindsay Mathieson Thanks for getting back. It’s just that the below warning that’s incorrect. Please note that the Function should still run and work fine.

We are working on fixing the error DOTNET-ISOLATED|8.0 has been deprecated as a language for Azure Functions and I will keep you posted about when the fix would be released.

Accepted answer

navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-28T03:58:53.21+00:00

@Lindsay Mathieson We appreciate your patience on this. Our Product Group team has confirmed that the fix has been published and this issue has been resolved for Python 3.11 and .NET Isolated 8. Please confirm if you still encounter the same issue.

We sincerely apologize for any inconvenience caused due to this.

**

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.
Please sign in to rate this answer.

3 people found this answer helpful.
Lindsay Mathieson 5 Reputation points

2023-09-28T09:47:11.3533333+00:00

That did the trick, thank you

navba-MSFT 23,810 Reputation points Microsoft Employee

2023-09-28T09:50:17.3166667+00:00

@Lindsay Mathieson . Thanks for your reply. I am glad that it helped.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to solve DOTNET-ISOLATED|8.0 has been deprecated as a language for Azure Functions

0 additional answers

Your answer