Skip to content

Commit 421672b

Browse files
xuehonggecfan
andauthored
Update articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md
Co-authored-by: Esther Fan <[email protected]>
1 parent 139d1fa commit 421672b

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,25 @@ The following errors commonly happen with a private storage account that's behin
106106
| Error building configuration in an external startup class | `"System.Private.CoreLib: Could not find a part of the path 'C:\home\site\wwwroot'."` |
107107
| Can't load workflows in the logic app resource | `"Encountered an error (ServiceUnavailable) from host runtime."` |
108108

109-
First, check out the environment variables WEBSITE_CONTENTAZUREFILECONNECTIONSTRING and WEBSITE_CONTENTSHARE. Make sure they point to the correct storage account and the correct file share. Make sure there is no typo, and storage account and file share were not accidently deleted.
109+
1. In the Azure portal, make sure that the storage account and file share still exist.
110+
111+
1. On the logic app resource menu, under **Settings**, select **Environment variables**.
112+
113+
1. On the **App settings** tab, find the settings named **WEBSITE_CONTENTAZUREFILECONNECTIONSTRING** and **WEBSITE_CONTENTSHARE**.
114+
115+
1. Check that these settings specify the correct storage account and file share, respectively. Make sure no spelling errors exist.
116+
117+
1. On the logic app resource menu, select **Diagnose and solve problems**. Find and run the following detectors: **Logic App Down or Reporting Errors** and **Network Troubleshooter**
118+
119+
These detectors provide insights and suggestions for fixing the problem.
120+
121+
The following list includes more troubleshooting actions that you can take to find the cause:
122+
123+
> [!NOTE]
124+
>
125+
> Your logic app resource and workflows aren't running when these errors occur,
126+
> so you can't use the Kudu console debugging capability in Azure for troubleshooting.
127+
110128

111129
Second, open the **Diagnose and solve problems** blade of the logic app. You can find and run these two detectors: **Logic App Down or Reporting Errors** and **Network Troubleshooter**. They will provide insights and suggest actions to fix the problem.
112130

0 commit comments

Comments
 (0)