Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0 for ServiceBus v5.22.2

[saraeq]

Description

When updating from v5.22.1 to v5.22.2 for package Microsoft.Azure.Functions.Worker.Extensions.ServiceBus we are receiving exceptions related to system.memory.data dll file which is not able to be found despite existing in the bin folder.

Have tried to preserve dll with

  <ItemGroup>
    <FunctionsPreservedDependencies Include="System.Memory.Data.dll" />
  </ItemGroup>

but error still persists.

Current workaround to downgrade to v5.22.1.

Project file setup:

	<PropertyGroup>
		<TargetFramework>net8</TargetFramework>
		<AzureFunctionsVersion>v4</AzureFunctionsVersion>
		<OutputType>Exe</OutputType>
		<ImplicitUsings>enable</ImplicitUsings>
		<Nullable>enable</Nullable>
		<LangVersion>latest</LangVersion>
		<DockerDefaultTargetOS>Linux</DockerDefaultTargetOS>
		<DockerfileContext>..\..</DockerfileContext>
	</PropertyGroup>

Error:

Steps to reproduce

• Update package version for Microsoft.Azure.Functions.Worker.Extensions.ServiceBus to v5.22.2
• Run function, observe system.memory.data exception

[satvu]

What host runtime version are you on? This looks like the following issue: Azure/azure-functions-host#10575.

[Frulfump]

The logs look like they might be from the Azure Functions Core Tools, which version do you have of that tool? Is it locally or in Azure you are seeing this issue?

(Images of text is annoying if it's not also presented with the text itself as you force others to use OCR tools to extract the text as no one will copy it by hand)

[saraeq]

What host runtime version are you on? This looks like the following issue: Azure/azure-functions-host#10575.

I am on runtime version 4.1036.2.2.

Have read through the issue you have linked, but it was only the workaround with downgrading the package that worked for me.
I cannot see that there are any permanent fix for this issue yet?

The issue is both locally and in Azure.

[Frulfump]

4.1036.2.2 is quite old I think but I'll let satvu continue that conversation (4.1036.2 is from September 2024 but was probably not deployed straight away https://github.com/Azure/azure-functions-host/releases/tag/v4.1036.2). But that runtime I don't think contains the fix for the referenced issue as I think that was a part of 4.1037.* releases fixed in this PR Azure/azure-functions-host#10610. Something that worked for us was checking if anything in our dependency graph pulled in System.Memory.Data version 8.0.0 and try to downgrade it (as you did) or remove it. Using lock files makes it easy to check what's pulling in what or trying dotnet nuget why System.Memory.Data if you are using .NET 8 SDK 8.0.400 or later.
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-nuget-why
But that special handling wasn't needed after 4.1037.* releases were deployed.

Locally you should be able to update the Azure Functions Core tools to the latest release by following the instructions here for Visual Studio Azure/azure-functions-host#10575 (comment)
and here for Linux MacOS or Windows Azure/azure-functions-host#10575 (comment)
How was your Azure Functions Core tools installed? I think some people have had issues with the MSI but a clean uninstall/installation seems to have fixed it for them.

There was a new release of Microsoft.Azure.Functions.Worker.Extensions.ServiceBus just now https://github.com/Azure/azure-functions-dotnet-worker/releases/tag/servicebus-extension-5.23.0 version 5.23.0 that updates some dependencies #3098

Microsoft.Azure.WebJobs.Extensions.ServiceBus to 5.17.0
Azure.Identity to 1.13.1
Microsoft.Extensions.Azure to 1.12.0

Maybe some of that bumping fixed your issue if we're lucky, but I think the main issue is the old runtime version so maybe some base Docker image update could be done?

[Frulfump]

@saraeq @satvu Any updates here?

[Frulfump]

@jviau maybe you can help out here as well?

[satvu]

What host runtime version are you on? This looks like the following issue: Azure/azure-functions-host#10575.

I am on runtime version 4.1036.2.2.

Have read through the issue you have linked, but it was only the workaround with downgrading the package that worked for me. I cannot see that there are any permanent fix for this issue yet?

The issue is both locally and in Azure.

@saraeq - you need to be on later versions of the runtime to fix this issue. Both our production runtime version and latest core-tools versions should be compatible.

Please update your core-tools version for local development. For your production environment, please make sure your base docker image is up to date as well.