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.

fabiocav · 2024-11-07T16:07:40Z

Keeping this open to track deployment.

OrlandoPaglione · 2024-11-11T03:16:11Z

Hi., all

"I spent a week dealing with the System.Data issue, and this solution solved it:

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

I would also like to know if there is a way to isolate the app from dependencies, as these types of errors undermine the system's credibility. With just a single tool update, everything can simply stop working, and you don’t get reliable error logs to understand what’s happening."

Would you like more information on isolating app dependencies in Azure Functions?

Thanks.
Orlando

richardhitchins · 2024-11-14T17:00:57Z

Downgrading Microsoft.Azure.WebJobs.Extensions.Storage from 5.3.3 to 5.3.2 worked for me

LockTar · 2024-11-23T11:48:59Z

Running .NET 8 in process.

This is working for me deploying in Azure but locally I still have another issue.

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

Any idea when a fix will be available?

Locally I still have the following issue:
Could not load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=8.0.0.0

rclark-christies · 2024-11-27T08:25:58Z

@LockTar this looks to be unrelated - but I resolved the same issue locally by updating to the latest Azure Functions Core Tools.

LockTar · 2024-11-27T08:46:30Z

@LockTar this looks to be unrelated - but I resolved the same issue locally by updating to the latest Azure Functions Core Tools.

I also think it's unrelated but everything was fine before upgrading to .NET 8. Tried your solution (didn't have the tools because I'm using visual studio 2022 latest with latest tools) but without luck. I will try to convert the project to isolated ASAP.

mattgwagner · 2024-11-28T02:02:01Z

This started blowing up my running Azure Function app even though I had not made any code changes or deployments in 3+ weeks. Incredibly frustrating for nothing that I changed!

System.IO.FileNotFoundException:
   at Azure.RequestFailedException.AppendContentAndHeaders (Azure.Core, Version=1.44.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Azure.RequestFailedException.CreateExceptionDetails (Azure.Core, Version=1.44.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Azure.RequestFailedException..ctor (Azure.Core, Version=1.44.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at Azure.Storage.Queues.MessagesRestClient+<EnqueueAsync>d__14.MoveNext (Azure.Storage.Queues, Version=12.19.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Azure.Storage.Queues.QueueClient+<SendMessageInternal>d__82.MoveNext (Azure.Storage.Queues, Version=12.19.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Azure.Storage.Queues.QueueClient+<SendMessageAsync>d__81.MoveNext (Azure.Storage.Queues, Version=12.19.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Extensions.Storage.Common.StorageQueueExtensions+<AddMessageAndCreateIfNotExistsAsync>d__0.MoveNext (Microsoft.Azure.WebJobs.Extensions.Storage.Queues, Version=5.3.1.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Queues.QueueProcessor+<CopyMessageToPoisonQueueAsync>d__14.MoveNext (Microsoft.Azure.WebJobs.Extensions.Storage.Queues, Version=5.3.1.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Queues.QueueProcessor+<HandlePoisonMessageAsync>d__13.MoveNext (Microsoft.Azure.WebJobs.Extensions.Storage.Queues, Version=5.3.1.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Host.Queues.QueueProcessor+<BeginProcessingMessageAsync>d__11.MoveNext (Microsoft.Azure.WebJobs.Extensions.Storage.Queues, Version=5.3.1.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Extensions.Storage.Common.Listeners.QueueListener+<ProcessMessageAsync>d__44.MoveNext (Microsoft.Azure.WebJobs.Extensions.Storage.Queues, Version=5.3.1.0, Culture=neutral, PublicKeyToken=92742159e12e44c8)

VladDerptastic · 2024-12-01T12:14:16Z

Keeping this open to track deployment.

Hey @fabiocav, sorry to bother, but do you know if this is this anywhere close to being resolved the 'proper' way?

MikeP707 · 2024-12-02T06:44:06Z

I have also the same problem when I try to use Microsoft.Azure.Functions.Worker.Extensions.Timer 4.3.1
Timer trigger attribute on TimerInfo.

Environment: dotnet-isolated
Dotnet: 8 and 9 the same
Error: Azure.Core: Could not load file or assembly 'System.Memory.Data, Version=6.0.0.0'

I tried solutions with _FunctionsSkipCleanOutput and Functions preserved dependencies but it doesn't work. It look like when I replace it by Http trigger it works.
Do you have any ideas how to fix this error or replace this timer by another one?

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

fabiocav reopened this Nov 7, 2024

fabiocav mentioned this issue Nov 7, 2024

Problem with Microsoft.Azure.Webjobs.Extensions version 5.3.3 Azure/azure-webjobs-sdk#3112

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

jsquire commented Oct 12, 2024

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

fabiocav commented Nov 7, 2024

OrlandoPaglione commented Nov 11, 2024 •

edited

Loading

richardhitchins commented Nov 14, 2024

LockTar commented Nov 23, 2024

rclark-christies commented Nov 27, 2024

LockTar commented Nov 27, 2024

mattgwagner commented Nov 28, 2024

VladDerptastic commented Dec 1, 2024 •

edited

Loading

MikeP707 commented Dec 2, 2024 •

edited

Loading

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

fabiocav commented Nov 7, 2024

OrlandoPaglione commented Nov 11, 2024 • edited Loading

richardhitchins commented Nov 14, 2024

LockTar commented Nov 23, 2024

rclark-christies commented Nov 27, 2024

LockTar commented Nov 27, 2024

mattgwagner commented Nov 28, 2024

VladDerptastic commented Dec 1, 2024 • edited Loading

MikeP707 commented Dec 2, 2024 • edited Loading

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

OrlandoPaglione commented Nov 11, 2024 •

edited

Loading

VladDerptastic commented Dec 1, 2024 •

edited

Loading

MikeP707 commented Dec 2, 2024 •

edited

Loading