Logic Apps (Standard) "Workflow design time could not be started"

Andrew Newman 6 Reputation points
2022-01-17T17:46:46.09+00:00

When I try opening the Logic Apps workflow in the designer then get the following error:

func host start --port 8000

Azure Functions Core Tools
Core Tools Version: 3.0.3904 Commit hash: c345f7140a8f968c5dbc621f8a8374d8e3234206 (64-bit)
Function Runtime Version: 3.3.1.0

[2022-01-17T17:38:20.547Z] A host error has occurred during startup operation '732f05fc-82d9-4c0b-a6a2-50ffa07284d4'.
[2022-01-17T17:38:20.548Z] System.Net.Http: Error while copying content to a stream. System.Private.CoreLib: Unable to read data from the transport connection: An existing connection was
forcibly closed by the remote host.. An existing connection was forcibly closed by the remote host.
Value cannot be null. (Parameter 'provider')

After about 5 minutes get the "Workflow design time could not be started" error displayed but the designer is displayed. However searching for built in connectors and triggers get "Failed to fetch" error.

Versions installed:

Vs code: 1.63.2 (system setup)
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.18363

azure-functions-core-tools: 3.0.3904
Azurite Extension version 3.15.0

Donet SDK

  1. 0.0-preview2-003131 [C:\Program Files\dotnet\sdk]
  2. 1.801 [C:\Program Files\dotnet\sdk]
  3. 1.416 [C:\Program Files\dotnet\sdk]
  4. 0.302 [C:\Program Files\dotnet\sdk]

I have added the global.json file to the project root:
{
"sdk": {
"version": "3.1.416",
"rollForward": "disable"
}
}

Have tried re-installing azure-functions-core-tools. (Originally had version 4 which I un-installed and installed version 3)

https://learn.microsoft.com/en-us/azure/azure-functions/functions-run-local?tabs=v3%2Cwindows%2Ccsharp%2Cportal%2Cbash%2Ckeda

When trying to run the following command:

npm install -g azure-functions-core-tools@3 --unsafe-perm true

Get this error:

node lib/install.js
attempting to GET "https://functionscdn.azureedge.net/public/3.0.3904/Azure.Functions.Cli.win-x64.3.0.3904.zip"
Error: self signed certificate in certificate chain
npm WARN rollback Rolling back readable-stream@2.3.7 failed (this is probably harmless): EPERM: operation not permitted, lstat 'C:\Users\xxxxx\AppData\Roaming\npm\node_modules\azure-functions-core-tools\node_modules'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! azure-functions-core-tools@3.0.3904 postinstall: node lib/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the azure-functions-core-tools@3.0.3904 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xxxxx\AppData\Roaming\npm-cache_logs\2022-01-17T17_33_56_430Z-debug.log

Any suggestions on what to try next?

Already tried everything on these similar cases:

https://issueexplorer.com/issue/Azure/logicapps/138
https://stackoverflow.com/questions/69932191/not-able-to-create-azure-logic-app-workflow-using-visual-studio-code

But so far not been able to fix.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,119 questions
Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,774 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Mohamed Ibrahim 10 Reputation points
    2023-02-01T15:32:36.0333333+00:00
    2 people found this answer helpful.

  2. Andrew Newman 6 Reputation points
    2022-01-18T11:59:42.337+00:00

    Resolved incident by copying the following folder from a computer that was working:

    C:\Users\xxxxxxx.azure-functions-core-tools\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows\1.1.30

    The breakthrough was running the func host start --port 8000 --verbose

    With the --verbose option could see that it was trying to download the extension bundle and failing probably because the firewall was blocking.

    1 person found this answer helpful.