Azure函数: Blob Storage emulator stopped working after moving to VS2022

Question

我有一个旧的 Azure Functions 项目 (v3)。它包含几个定时器触发的功能。他们停止了 VS2022 的工作。您可以看到下面的日志。如果我通过 VS2022 创建一个新的 Functions 项目，它将正常工作。看起来蓝铜矿也启动得很好。设置“AzureWebJobsStorage”等于“UseDevelopmentStorage=true”。我能做什么？

[2022-01-06T10:17:15.675Z] Host lock lease acquired by instance ID '000000000000000000000000DC2A3C3E'.
[2022-01-06T10:17:35.554Z] The listener for function 'Function1' was unable to start.
[2022-01-06T10:17:35.556Z] The listener for function 'Function1' was unable to start. Azure.Storage.Blobs: Service request failed.
[2022-01-06T10:17:35.557Z] Status: 500 (Internal Server Error)
[2022-01-06T10:17:35.557Z]
[2022-01-06T10:17:35.558Z] Headers:
[2022-01-06T10:17:35.559Z] Server: Azurite-Blob/3.14.1
[2022-01-06T10:17:35.560Z] ETag: "0x234B8B049DD4280"
[2022-01-06T10:17:35.561Z] x-ms-blob-type: BlockBlob
[2022-01-06T10:17:35.562Z] x-ms-lease-state: available
[2022-01-06T10:17:35.562Z] x-ms-lease-status: unlocked
[2022-01-06T10:17:35.563Z] x-ms-client-request-id: a3bc0141-7bcb-420c-84a9-eadf86f8c685
[2022-01-06T10:17:35.564Z] x-ms-request-id: 88474d4b-bc15-4f45-95d5-0a01682d883d
[2022-01-06T10:17:35.565Z] x-ms-version: 2020-10-02
[2022-01-06T10:17:35.566Z] Accept-Ranges: bytes
[2022-01-06T10:17:35.566Z] Date: Thu, 06 Jan 2022 10:17:35 GMT
[2022-01-06T10:17:35.567Z] x-ms-server-encrypted: true
[2022-01-06T10:17:35.570Z] x-ms-blob-content-md5: jhxvLoUrRfc2dXn/gXokig==
[2022-01-06T10:17:35.570Z] Connection: keep-alive
[2022-01-06T10:17:35.571Z] Keep-Alive: REDACTED
[2022-01-06T10:17:35.572Z] Last-Modified: Tue, 28 Dec 2021 11:10:44 GMT
[2022-01-06T10:17:35.573Z] Content-Length: 115
[2022-01-06T10:17:35.574Z] Content-Type: application/octet-stream
[2022-01-06T10:17:35.574Z] Content-MD5: jhxvLoUrRfc2dXn/gXokig==

更新
我在同一个项目中添加了一些新功能。他们工作得很好。我更改了函数和方法名称，旧函数也开始工作。看起来它在某个地方缓存了名称。我尝试过干净重建，但没有帮助。我不知道为什么它不适用于旧名称。

Answer 1

我能够通过使用Azure Storage Explorer解决这个问题并删除本地存储blob容器中azure-webjobs-hosts下的相关blob文件夹

根文件夹位于:本地和附加>存储帐户>(模拟器 - 默认端口)> Blob 容器 -> azure-webjobs-hosts

确保项目已打开，否则存储资源管理器可能无法加载容器。

删除后，问题函数开始按预期运行