Azure Functions - Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0 #10575

jsquire · 2024-10-12T16:46:45Z

Issue Transfer

This issue has been transferred from the Azure SDK for .NET repository, #46577.

Please be aware that @fhtino is the author of the original issue and include them for any questions or replies.

Details

Library name and version

Azure.Data.Tables 12.9.1 and Azure.Storage.Blobs 12.22.2

Describe the bug

Cannot use Azure.Data.Tables and Azure.Storage.Blobs in the same Azure Functions project in VS 2022. When I use the TableClient I get

System.IO.FileNotFoundException: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.
File name: 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   at Azure.Core.RequestContent.Create(Object serializable, ObjectSerializer serializer)
   at Azure.Core.RequestContent.Create(Object serializable)
   at Azure.Data.Tables.TableClient.CreateIfNotExistsAsync(CancellationToken cancellationToken)
   at azfunct1.HelloWorld.Run(HttpRequest req, ILogger log) in xxxxxxx\az-func-cannot-load-assembly\azfunct1\HelloWorld.cs:line 29

var tsc = new TableServiceClient("UseDevelopmentStorage=true");
var tabc = tsc.GetTableClient("zzztest1");
await tabc.CreateIfNotExistsAsync();

Sample project with the issue:
https://github.com/fhtino/publicissues/tree/main/az-func-cannot-load-assembly

Workaround: place _FunctionsSkipCleanOutput in the project file:

<PropertyGroup>
	<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

Expected behavior

no errors

Actual behavior

Exception: System.Memory.Data, Version=6.0.0.0 not found

Reproduction Steps

sample here: https://github.com/fhtino/publicissues/tree/main/az-func-cannot-load-assembly

Environment

Visual Studio 2022 17.11.5
Azure Functions Core Tools / Core Tools Version: 4.0.6518 (64-bit) / Function Runtime Version: 4.35.4.23179

The text was updated successfully, but these errors were encountered:

nodeomega · 2024-10-14T10:46:22Z

Can confirm. Also facing this issue.

Workaround I have seems to be having System.Memory.Data 6.0.0 installed as a separate NuGet package, building the solution, and copying the System.Memory.Data.dll file to the bin subdirectory in the bin folder, at least in Debug. (I assume Release would be the same way).

Which leads to a folder structure like bin\Debug\net8.0\bin, where I had to copy the dll from bin\Debug\net8.0

For whatever reason, this dependency isn't getting copied to that bin subfolder.

Side effect: Any time I make a change to the Azure Function project and rebuild, the copied System.Memory.Data.dll file disappears, and the error pops up again.

@fhtino - FYI.

Rudresh-Dongre-Contractor · 2024-10-17T07:19:27Z

Facing the same issue recently while trying to use Azure.Storage.Blobs

Dave-DRX · 2024-10-17T12:43:47Z

Having same issue with Microsoft.Azure.WebJobs.Extensions.Storage.Queues.

System.Private.CoreLib: Exception has been thrown by the target of an invocation. Microsoft.Azure.WebJobs.Extensions.Storage.Queues: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral. The system cannot find the file specified.

bishwaranjans · 2024-10-17T13:30:52Z

I am also facing the same issue

Dave-DRX · 2024-10-18T00:35:22Z

The prescribed workaround (see above: "<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>") worked.
I guess I need to update to an isolated process, as recommended by Microsoft, sooner than I thought.

sonofsmog · 2024-10-21T04:52:46Z

Same issue with using Azure.Security.KeyVault.Secrets and callingSecretClient.GetSecretAsync. @nodeomega's workaround worked for me. Good looking out. Hopefully this gets fixed soon.

mcremer-able · 2024-10-21T06:53:59Z

Wer are using nodejs and as such can not use @nodeomega 's workaround.
Is there any way to maybe downgrade, so it can work again?

shibayan · 2024-10-23T06:52:48Z

Alternative workaround

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

Y-Sindo · 2024-10-28T04:15:36Z

Having the same issue for the latest Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0 version. It blocks users from using managed identity to connect to SignalR Service.

DavidKoolen · 2024-10-28T11:25:14Z

We have the same issue with Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0. Downgrade to 1.14.1 resolves the issue and we can use the System-assigned managed identity again.

sastru · 2024-10-28T16:02:16Z

Alternative workaround

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

I can confirm that this alone as the single change, made it work as expected.

stasaristic · 2024-10-30T11:03:36Z

We have the same issue with Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0. Downgrade to 1.14.1 resolves the issue and we can use the System-assigned managed identity again.

Had the same issue, this is the only thing that solved it. Unfortunately version 1.15.0 kept giving me: Microsoft.Azure.WebJobs.Extensions.EventHubs: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral'. The system cannot find the file specified.

Y-Sindo · 2024-10-30T11:14:36Z

Hi @jsquire , the workarounds that add some properties in the project file still don't work for Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0.

The not working workarounds include:

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

If you need any other information from me, please let me know.

Arash-Sabet · 2024-10-31T01:54:18Z

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

This workaround did not work. We need a permanent solution. This issue must be addressed ASAP as it's a roadblock.

jameseedi · 2024-11-05T08:41:14Z

I spent a significant amount of time resolving an issue involving dependencies on System.Memory.Data 6.0.0. Locally, I managed to get things working by manually replacing the DLL with version 6.0.0 in the AzureFunctionsTools folder at:

C:\Users\User\AppData\Local\AzureFunctionsTools\Releases\4.100.0\cli_x64

However, on Azure, this isn't possible due to the lack of access for patching DLLs directly. After extensive troubleshooting, I discovered that the recent upgrade to Microsoft.Azure.Functions.Worker.Extensions.SignalRService 1.15.0 was the root cause. Downgrading to 1.14.1 resolved the issue.

This complex dependency setup clearly needs addressing. Ideally, we should also have more control over configuration in Azure to facilitate such troubleshooting. If there are any ways to achieve this, please let me know.

Having used Azure Functions since v1, I’ve found it to be a convenient but often frustrating service. The migration paths (e.g., isolated functions, v1 to v2) have been rocky, and these issues make maintaining reliable services challenging. I encourage proactive measures to improve stability in the Azure Functions ecosystem. 🙏

pingu2k4 · 2024-11-06T13:34:41Z

I've got the same issue here regarding the SignalRService package. None of the workarounds fix anything in this instance, other than reverting to 1.14.1, including things I had tried from other places (for example using assembly binding redirects)

Would love to see a resolution for this.

fabiocav · 2024-11-07T08:08:18Z

The current mitigation is to either downgrade the package bringing the dependency, or update the project configuration mentioned in the issue if using the .NET in-proc model:

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

For the .NET Isolated model, the impacted package (SignalR) must be downgraded. We will work with the appropriate team to delist in the meantime, as this was an invalid update. We'll also be working with them to ensure this issue is prevented in the future.

A fix for this will be rolling out with the next host deployment. Thank you all for the report and patience.

pregress · 2025-03-25T08:00:47Z

Same issue when upgrading to: https://github.com/Azure/azure-functions-dotnet-worker/releases/tag/servicebus-extension-5.22.2
From version https://github.com/Azure/azure-functions-dotnet-worker/releases/tag/servicebus-extension-5.22.1

Rolling back fixed it, running on isolated workers, linux, dotnet 9 (build with latest sdk), deployed in west europe

What's a valid test we can run to prevent this? So that we can catch this before deploying it?

liliankasem · 2025-03-25T20:27:58Z

For v4.1037 of the host, Core Tools is not yet released but this is in progress (I believe this will be version 4.0.7030)

@liliankasem: What is the timeline/ETA for the 4.0.7030 release? (see also comment in other bug/thread) - #10930 (comment)

I've been told it is due by end of this week but I can't promise it will be - so end of this week or potentialy early next.

SRE-Agent · 2025-03-25T20:56:33Z

This issue appears to be a duplicate of the broader tracking issue related to assembly resolution errors in the Azure Functions runtime environment with regards to System.Memory.Data. Other users have faced identical failures when using overlapping SDKs (e.g., Azure.Data.Tables & Storage.Blobs).

If open bugs escalation aggregation let issue Aggregate recomplet assign lookup STRICT_TRACK!

RobK410 · 2025-03-26T03:13:20Z

Just adding my two cents, as I just upgraded Microsoft.Azure.WebJobs.Extensions.ServiceBus to 5.22.2 and blew up all my Azure functions. Rolling back to 5.22.1 fixed the issue.

Microsoft.Azure.WebJobs.Extensions.ServiceBus: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyREDACTED

System.IO.FileNotFoundException:
   at Microsoft.Azure.WebJobs.ServiceBus.Config.ServiceBusExtensionConfigProvider.Initialize (Microsoft.Azure.WebJobs.Extensions.ServiceBus, Version=5.16.5.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Microsoft.Azure.WebJobs.Host.DefaultExtensionRegistryFactory.Create (Microsoft.Azure.WebJobs.Host, Version=3.0.41.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\DefaultExtensionRegistryFactory.cs:38)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd (System.Collections.Concurrent, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService (Microsoft.Extensions.DependencyInjection.Abstractions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService (Microsoft.Extensions.DependencyInjection.Abstractions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Azure.WebJobs.WebJobsServiceCollectionExtensions+<>c.<AddWebJobs>b__3_6 (Microsoft.Azure.WebJobs.Host, Version=3.0.41.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35: D:\a\_work\1\s\src\Microsoft.Azure.WebJobs.Host\Hosting\WebJobsServiceCollectionExtensions.cs:101)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd (System.Collections.Concurrent, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService (Microsoft.Extensions.DependencyInjection, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService (Microsoft.Extensions.DependencyInjection.Abstractions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.Azure.WebJobs.Script.WebHost.WebJobsScriptHostService+<UnsynchronizedStartHostAsync>d__58.MoveNext (Microsoft.Azure.WebJobs.Script.WebHost, Version=4.1036.0.0, Culture=neutral, PublicKeyToken=null: /src/azure-functions-host/src/WebJobs.Script.WebHost/WebJobsScriptHostService.cs:351)

FedyaNyet · 2025-03-27T01:55:31Z

this following helped me:

npm install -g azure-functions-core-tools@latest --unsafe-perm true

tlogik · 2025-03-27T09:27:28Z

~~@RobK410 @hunyhabib where did you guys get Microsoft.Azure.WebJobs.Extensions.ServiceBus in version 5.22.2 ?~~

According to nuget the latest is 5.16.5
https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.ServiceBus/#versions-body-tab

~~Im on 5.16.5 and it has blown up with the assembly issues.~~
I can see that my solution was updated to 5.22.2 and then, as experienced by @RobK410 @hunyhabib it blows up.
Will downgrade to 5.22.1 and verify if the problem disappears

This is from Azure:

Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified. 

Failed Method: Microsoft.Azure.WebJobs.ServiceBus.Config.ServiceBusExtensionConfigProvider.Initialize

However the dll is definely part of the deployed artifact.
Checked the version of the dll from the deployed artifact:

versioninfo System.Memory.Data.dll
System.Memory.Data.dll
	FileVersionInfo.FileVersion:	6.0.21.52210
	FileVersionInfo.ProductVersion:	6.0.0+4822e3c3aa77eb82b2fb33c9321f923cf11ddde6

My artifact is build in Azure Devops using dotnet Build and Publish on Ubuntu Latest.

In azure running NET 9 - Isolated function on a Linux AppService Plan - so implicitly in a docker container.

Running locally it works just fine using: func host start (MAC OS)

hunyhabib · 2025-03-27T09:28:13Z

as @RobK410 i just upgraded Microsoft.Azure.WebJobs.Extensions.ServiceBus ** to ** 5.22.2 function started failing i tried @sastru change + adding System.Memory.Data Nuget Package but still failed.. the only thing worked was rolling back to version 5.22.1 .. I am using Azure Function Isolated with .Net 8 running it as docker container.

TheBlakeOmega · 2025-03-28T11:28:36Z

Is there any update on this topic?
I incurred in this problem yesterday, but my project is an azure function in python. I'm confused because i started another azure function project in c# and all run properly, but when i switch back to python one this error raises:

[2025-03-28T10:14:41.551Z] A host error has occurred during startup operation 'f2208242-0b3e-470c-ab0b-f59a1da2536f'.
[2025-03-28T10:14:41.552Z] Azure.Core: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.
[2025-03-28T10:14:41.574Z] Failed to stop host instance '7783d95b-45f1-443c-b814-e58a4766acd8'.
[2025-03-28T10:14:41.576Z] Microsoft.Azure.WebJobs.Host: The host has not yet started.

hooverdirt · 2025-03-28T11:46:43Z

Is there any update on this topic? I incurred in this problem yesterday, but my project is an azure function in python. I'm confused because i started another azure function project in c# and all run properly, but when i switch back to python one this error raises:

[2025-03-28T10:14:41.551Z] A host error has occurred during startup operation 'f2208242-0b3e-470c-ab0b-f59a1da2536f'. [2025-03-28T10:14:41.552Z] Azure.Core: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified. [2025-03-28T10:14:41.574Z] Failed to stop host instance '7783d95b-45f1-443c-b814-e58a4766acd8'. [2025-03-28T10:14:41.576Z] Microsoft.Azure.WebJobs.Host: The host has not yet started.

What I've seen is this - Mac/Brew

Python 3.11.9 --- issues - possible to upgrade to most recent core utils BUT need to deploy grpc manually. If not comfortable - wait for official release
Python 3.11.10 -- no issues with upgrade to most recent core utils.

(Hope this helps)

TheBlakeOmega · 2025-03-28T11:54:40Z

i'm using Python 3.11.9 and i need quickly to fix this issue, i can't waint for official release. What i have to do to deploy grpc manually ( and what is grpc?)

hooverdirt · 2025-03-28T12:40:19Z

i'm using Python 3.11.9 and i need quickly to fix this issue, i can't waint for official release. What i have to do to deploy grpc manually ( and what is grpc?)

I did this earlier with another dev - it should work if not --

Check your current function-core-tools version. Make note of this.

Do your usual brew upgrade for your function-core-tools. It should get you a 68xx version - MAKE NOTE OF THIS.
If you run func start now - you should get a different error - complaining about grpc/symbol missing. Make note of the location/folder location (it will complain about an so file)
Make sure you are in a venv or use the global python version - it has to match the python version that you are using to run func start
pip uninstall grpcio
export GRPC_PYTHON_LDFLAGS=" -framework CoreFoundation"
pip install grpcio --no-binary :all:
when done, check the location where the libraries where compiled to thru pip show grpcio
then copy the contents of the grpc folder to the brew folder that reported the issue (I think just copying the so file is good enough)

I don't have screenshots of step 8 - but the folder names where the new compiled files are matches the one in brew/cellar folder. Just copy/replace/force.

Run func start and you should be good to go - note that you'll get weird errors/warnings but that should get you going with your local azurite.

I'm currently investigating what the effort is to move to 3.11.10

Strandfelt · 2025-03-28T12:41:47Z

This is starting to become a real issue for os. Starting this week, we have been getting weird YARP exceptions in our Functions. Upgrading to the last versions of the Worker packages solved this. However, now, we are experiencing this issue with the new package versions, leading to a catch-22 where we are failing both on the newest version but also when rolling back.

alexwiese · 2025-04-01T12:40:28Z

I think 4.1037 is pretty much fully rolled out at this point (it was indeed slowed down due to some hotfix requirements).

@liliankasem we have function apps in Australia East and Australia South East that are hitting this issue and are still on v4.1036.
We have tried stop/starting and restarting multiple times and they are not upgrading to 4.1037.

Can we get an ETA on the upgrade across Azure?
What is the reason it is taking so long to upgrade?

martin-poelzl-AP · 2025-04-01T13:12:09Z

Our functions on consumption plan are updated. Those on a dedicated appservice plan are still on v4.1036
When will they get the update?

satvu · 2025-04-01T17:42:36Z

@alexwiese Can you share some information about your environment?

@martin-poelzl-AP Are you on Windows or Linux? Can you share a bit more about your hosting plan?

alexwiese · 2025-04-01T23:03:20Z

@alexwiese Can you share some information about your environment?

We have function apps across AU East and AU South East.
All of them are on dedicated app service plans.
A mix of Linux and windows.

martin-poelzl-AP · 2025-04-02T05:57:45Z

@satvu It is a P0v3 plan on linux (not using container images). We use the same plan for multiple functions. All these are on 1036

satvu · 2025-04-02T23:32:00Z

4.1037 and higher versions are not yet available on Linux Dedicated for dotnet-isolated customers. Our current ETA for these customers is between April 18-April 25.

For those who are not on dotnet-isolated in Linux Dedicated and are unable to pick up a new host version on restart, please open a support ticket (through the Azure portal) for further investigation.

satvu · 2025-04-02T23:33:38Z

@alexwiese Can you share some information about your environment?

We have function apps across AU East and AU South East. All of them are on dedicated app service plans. A mix of Linux and windows.

@alexwiese The windows dedicated apps should be able to pick up a new version on restart - if you're still unable to pick up 4.1037, please open a support ticket so we can investigate.

JasonHough75 · 2025-04-07T10:39:50Z

Hi guys - i am using a python blolb trigger and the issue has just started. http trigger is fine though. I am getting sytem.memory.data error. any idea of a fix ? I am using tools verion 4.0.5907 and python 3.10.11 - and these cannot be changed easy. help would be amazing. this is the same on a new project and also an older project. I have also added "_functionSkipCleanOuutput" in the host.json file and this did not work and said its not allowed.

vitorlinares · 2025-04-07T12:01:19Z

4.1037 and higher versions are not yet available on Linux Dedicated for dotnet-isolated customers. Our current ETA for these customers is between April 18-April 25.

For those who are not on dotnet-isolated in Linux Dedicated and are unable to pick up a new host version on restart, please open a support ticket (through the Azure portal) for further investigation.

@satvu, does this apply to functions hosted in container apps too?
We are facing the very same issue with our functions running in containers and I'm wondering if this will also be fixed between 18-25 April too.

hooverdirt · 2025-04-07T16:30:56Z

Hi guys - i am using a python blolb trigger and the issue has just started. http trigger is fine though. I am getting sytem.memory.data error. any idea of a fix ? I am using tools verion 4.0.5907 and python 3.10.11 - and these cannot be changed easy. help would be amazing. this is the same on a new project and also an older project. I have also added "_functionSkipCleanOuutput" in the host.json file and this did not work and said its not allowed.

Try what I did (as I mentioned I did this with another dev as well): #10575 (comment)

satvu · 2025-04-07T18:17:33Z

@JasonHough75 You need core-tools version 4.0.703 which has host version 4.1037. This is the latest released version.

@VictorLinares dotnet-isolated images (see tags on docker hub) are currently in the process of being updated and should be done by April 18-25 as well.

cfeenstra1024 · 2025-04-08T09:53:43Z

@satvu Thanks for the info.
I have to say that this is very frustrating as a developer. It takes hours to find the root cause of an issue like this as an Azure Function developer, especially if the version increase was part of a bigger task (in my case a migration from the in-process model to the isolated model).
I don't really understand how a new package can be released to the public, if Azure itself is not ready to consume it. In my opinion the package should have been withdrawn until it can be used in Azure.

jsquire mentioned this issue Oct 12, 2024

[BUG] Azure Functions - Azure.Core: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0 Azure/azure-sdk-for-net#46577

Closed

microsoft-github-policy-service bot added the Needs: Triage (Functions) label Oct 12, 2024

This comment has been minimized.

Sign in to view

Y-Sindo mentioned this issue Oct 29, 2024

Support SignalR trigger return value Azure/azure-functions-dotnet-worker#2771

Merged

7 tasks

fabiocav transferred this issue from Azure/azure-functions-dotnet-worker Oct 29, 2024

fabiocav mentioned this issue Oct 30, 2024

.NET 8 In-proc App: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0, Culture=neutral' #10567

Closed

m-redding mentioned this issue Oct 31, 2024

[BUG] BinaryData.ToString() throws nullreference exception after upgrading Microsoft.Extensions.Azure/Azure.Core Azure/azure-sdk-for-net#46444

Closed

surgupta-msft mentioned this issue Nov 1, 2024

Function startup fails when using System.Memory.Data 6.0.0 Azure/azure-functions-core-tools#2872

Closed

pingu2k4 mentioned this issue Nov 6, 2024

SignalRService crashes with "Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0" Azure/azure-functions-dotnet-worker#2833

Open

fabiocav removed the Needs: Triage (Functions) label Nov 7, 2024

fabiocav self-assigned this Nov 7, 2024

fabiocav mentioned this issue Nov 7, 2024

Updating System.Memory.Data reference #10610

Merged

9 tasks

fabiocav closed this as completed in #10610 Nov 7, 2024

Azure deleted a comment from SRE-Agent Mar 25, 2025

RobK410 mentioned this issue Mar 27, 2025

FileNotFoundException System.Memory.Data related to 5.22.2 Azure/azure-functions-dotnet-worker#3008

Closed

This comment has been minimized.

Sign in to view

AndYggdrasil mentioned this issue Mar 28, 2025

Failed to proxy request with ForwarderError: ResponseBodyDestination The response ended prematurely #10969

Closed

mlankamp mentioned this issue Apr 14, 2025

Updating Microsoft.Azure.Functions.Worker.Extensions.ServiceBus from 5.22.1 to 5.22.2 Azure/azure-functions-dotnet-worker#3028

Open

Azure Functions - Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0 #10575

Azure Functions - Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0 #10575

Comments

jsquire commented Oct 12, 2024

Issue Transfer

Please be aware that @fhtino is the author of the original issue and include them for any questions or replies.

Details

Library name and version

Describe the bug

Expected behavior

Actual behavior

Reproduction Steps

Environment

nodeomega commented Oct 14, 2024 • edited Loading

Rudresh-Dongre-Contractor commented Oct 17, 2024

Dave-DRX commented Oct 17, 2024

bishwaranjans commented Oct 17, 2024

Dave-DRX commented Oct 18, 2024

sonofsmog commented Oct 21, 2024

mcremer-able commented Oct 21, 2024

shibayan commented Oct 23, 2024

This comment has been minimized.

Y-Sindo commented Oct 28, 2024

DavidKoolen commented Oct 28, 2024

sastru commented Oct 28, 2024 • edited Loading

stasaristic commented Oct 30, 2024

Y-Sindo commented Oct 30, 2024

Arash-Sabet commented Oct 31, 2024 • edited Loading

jameseedi commented Nov 5, 2024

pingu2k4 commented Nov 6, 2024

fabiocav commented Nov 7, 2024 • edited Loading

pregress commented Mar 25, 2025 • edited Loading

liliankasem commented Mar 25, 2025

SRE-Agent commented Mar 25, 2025

RobK410 commented Mar 26, 2025

FedyaNyet commented Mar 27, 2025

tlogik commented Mar 27, 2025 • edited Loading

hunyhabib commented Mar 27, 2025 • edited Loading

TheBlakeOmega commented Mar 28, 2025

hooverdirt commented Mar 28, 2025

TheBlakeOmega commented Mar 28, 2025

hooverdirt commented Mar 28, 2025

Strandfelt commented Mar 28, 2025

This comment has been minimized.

alexwiese commented Apr 1, 2025 • edited Loading

martin-poelzl-AP commented Apr 1, 2025

satvu commented Apr 1, 2025

alexwiese commented Apr 1, 2025

martin-poelzl-AP commented Apr 2, 2025

satvu commented Apr 2, 2025

satvu commented Apr 2, 2025

JasonHough75 commented Apr 7, 2025 • edited Loading

vitorlinares commented Apr 7, 2025

hooverdirt commented Apr 7, 2025

satvu commented Apr 7, 2025

cfeenstra1024 commented Apr 8, 2025

nodeomega commented Oct 14, 2024 •

edited

Loading

sastru commented Oct 28, 2024 •

edited

Loading

Arash-Sabet commented Oct 31, 2024 •

edited

Loading

fabiocav commented Nov 7, 2024 •

edited

Loading

pregress commented Mar 25, 2025 •

edited

Loading

tlogik commented Mar 27, 2025 •

edited

Loading

hunyhabib commented Mar 27, 2025 •

edited

Loading

alexwiese commented Apr 1, 2025 •

edited

Loading

JasonHough75 commented Apr 7, 2025 •

edited

Loading