Azure-functions-host: Metadata generation failed. Exit code: '-1073741502' Error: '' #6769

[krillehbg]

nugetpackagesmicrosoft.azure.webjobs.script.extensionsmetadatagenerator1.2.0buildMicrosoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets(37,5): error : Metadata generation failed. Exit code: '-1073741510

The problems occurs when having
.nugetpackagesmicrosoft.azure.webjobs.script.extensionsmetadatagenerator1.2.0

Removing this folder and only running package 1.1.8 works fine to build again.

[the-castman]

I am getting the same error but with 1.1.8 and with Microsoft.NET.Sdk.Functions 3.0.9

[error]C:\Windows\ServiceProfiles\NetworkService\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.1.8\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets(37,5): Error : Metadata generation failed. Exit code: '-1073741502' Error: ''.

I am getting this om my Azure Devops build pipeline and very sporadic och sudden, using the clean option on the pipeline doesn´t help, This started to appear since one week ago. Sometimes after waiting a while, triggering a new build it would succeed. This is starting to get really annoying!

[mikechu-pennfoster]

Thanks for the pointer @krillehbg This was exactly the issue on my local.

@the-castman I wonder if the Azure DevOps clean option is doing what we hope in giving us a completely fresh build env. I wonder if waiting a while then triggering a new build is (by chance) assigning a different build agent in the MS infrastructure. :thinking:

[LeonsBuntis]

I'm getting same error with Microsoft.NET.Sdk.Functions Version="1.0.38".

There is no reference to microsoft.azure.webjobs.script.extensionsmetadatagenerator in my project, but I have encountered this issue in Azure Devops. Seems that if the package is downloaded by other projects that are built on same build agent it breaks my project.

The Azure DevOps clean option does not clean up shared nuget packages that are stored in "c:users\%username%\.nugetpackages".

There is no such issue in newer version 1.2.1. of microsoft.azure.webjobs.script.extensionsmetadatagenerator, but the 1.2.0 must be cleaned up otherwise I still get same error.

Is there any workaround for this issue, other than forcing other teams that use same build agents to upgrade and cleanup packages?