Following my last blog post, Logic App Standard Engine Error: System.Private.CoreLib: Could not find a part of the path ‘C:\home\site\wwwroot’, we had the following error thrown by the Logic App Standard Engine that was enabling it to start properly:
System.Private.CoreLib: Access to the path ‘C:\home\data\Functions\secrets\Sentinels’ is denied.
📝 One-Minute Brief
Logic Apps Standard may fail to start with the error “System.Private.CoreLib: Access to the path C:\home\data\Functions\secrets\Sentinels is denied.” This post explains the root cause of this issue and shows the configuration change required to restore normal execution.
Cause
This error typically occurs when you disable Storage Account Key Access for the Storage Account.
If you disable the storage account key, the Logic App Standard won’t be able to create or run the workflow or even start the engine properly. This configuration type is not supported.
Solution
The solution is simple: you must enable the Storage Account Key Access on your Storage Account.
To do that, you just need to:
- You can access the Overview page of your Storage Account by clicking on the link for the Storage account key access property.
- Or, in your Storage Account, from the left menu, click Settings > Configurations.
- On the Configuration page, make sure you select the Enabled option on the Allow storage account key access property.
- Click Update.
I hope you find this helpful! If you liked the content or found it useful and want to help me write more, you can buy (or help me buy) my son a Star Wars Lego!
Storage Account Key Access is Enabled in my case. But still getting same error
did you find any resolution. same for me
same error fr me. Allow storage account key access is enabled. any resolution?
https://docs.azure.cn/en-us/logic-apps/deploy-single-tenant-logic-apps-private-storage-account
On the App settings tab, add the WEBSITE_CONTENTOVERVNET app setting, if none exist, and set the value to 1.
Still error persist have added WEBSITE_CONTENTOVERVNET and storage key access enabled
Still error persisted after App settings and Storage key access
TJ was right! Thanks for this hint!