logicapps: Cannot start the workflow designer in VS Code

Describe the Bug

I’m developing Logic Apps in VS Code on a Mac. Starting today I cannot load the workflow designer.

When I try to open a workflow using the context menu “Open in Designer” I get the usual message "Starting workflow design time api. It might take a few seconds.". In the output window I can see the following:

[2023-01-31T13:27:44.554Z] A host error has occurred during startup operation 'c2a7523a-39b6-4371-b479-365d12600950'.
[2023-01-31T13:27:44.554Z] Microsoft.WindowsAzure.ResourceStack: Unable to load shared library 'advapi32.dll' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: dlopen(libadvapi32.dll, 0x0001): tried: 'libadvapi32.dll' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibadvapi32.dll' (no such file), '/usr/lib/libadvapi32.dll' (no such file, not in dyld cache), 'libadvapi32.dll' (no such file), '/usr/local/lib/libadvapi32.dll' (no such file), '/usr/lib/libadvapi32.dll' (no such file, not in dyld cache).
Value cannot be null. (Parameter 'provider')
2:41:46 PM: Error: connect ECONNREFUSED 127.0.0.1:8000
2:42:44 PM: Running command: "func host start --port 8000"...

I can also see that a func process is being started and then quickly terminated when looking in the Activity Monitor.

This has been reproduced on several MacBooks, using Intel (Core i7) as well as Apple (M1 Pro) silicon. Same result.

Yesterday, January 30th, this was working fine. Today on Jan 31, it’s not.

Plan Type

Standard

Steps to Reproduce the Bug or Issue

Open any logic app standard project
Try to open a workflow by right-clicking on a “workflow.json” file and then select “Open in Designer”
View output pane (Shift+CMD+U on Mac)

Workflow JSON

{
  "definition": {
    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
    "actions": {},
    "contentVersion": "1.0.0.0",
    "outputs": {},
    "triggers": {}
  },
  "kind": "Stateful"
}

Screenshots or Videos

Screenshot 2023-01-31 at 15 11 56

Additional context

No response

AB#16959559 Relates #722

About this issue

Original URL
State: closed
Created a year ago
Comments: 17

Most upvoted comments

I’m trying to specify

“version”: “2.0”, “extensionBundle”: { “id”: “Microsoft.Azure.Functions.ExtensionBundle.Workflows”, “version”: “[1.*, 1.8.9)”

But this results in the broken 1.3.7 extension being downloaded.

I’ve reverted to 1.2.18 as per the original workaround for this issue. Which is working.

For those just stumbling upon this issue:

You need to update host.json in both workflow-designtime and in the project level host.json

Change

“extensionBundle”: { “id”: “Microsoft.Azure.Functions.ExtensionBundle.Workflows”, “version”: “[1.*, 2…0.0)” },

“extensionBundle”: { “id”: “Microsoft.Azure.Functions.ExtensionBundle.Workflows”, “version”: “[1.*, 1.2.18)” },

This should allow editing and running your workflows locally while the issue is worked on.

axiomitdavid on Apr 14, 2023

Hi all, thanks for raising this issue and for collaborating on the thread. I am able to repro the issue and will update you as soon as this is fixed. Please keep using the workaround stated above

ccastrotrejo on Feb 2, 2023

Need to re-open this. Issue is now occurring with new Extension version 1.11.15

9:47:14 AM: Running command: “func host start --port 8003”…

Azure Functions Core Tools Core Tools Version: 4.0.5095 Commit hash: N/A (64-bit) Function Runtime Version: 4.16.5.20396

[2023-04-13T23:47:17.810Z] A host error has occurred during startup operation ‘9d2345e3-1adc-4fd7-9da4-f69e61c38c5b’. [2023-04-13T23:47:17.810Z] Microsoft.Azure.Workflows.EventSource.Edge: The type initializer for ‘Microsoft.Azure.Workflows.Common.Logging.FlowLog’ threw an exception. Microsoft.WindowsAzure.ResourceStack: Unable to load shared library ‘advapi32.dll’ or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: dlopen(libadvapi32.dll, 0x0001): tried: ‘libadvapi32.dll’ (no such file), ‘/System/Volumes/Preboot/Cryptexes/OSlibadvapi32.dll’ (no such file), ‘/usr/lib/libadvapi32.dll’ (no such file, not in dyld cache), ‘libadvapi32.dll’ (no such file), ‘/usr/local/lib/libadvapi32.dll’ (no such file), ‘/usr/lib/libadvapi32.dll’ (no such file, not in dyld cache). Value cannot be null. (Parameter ‘provider’)

axiomitdavid on Apr 13, 2023

Ok, I’ve run into this as of today as well (as well as one of my other developers)

All existing projects as well as brand new empty ones have this issue.

The one thing I did find that will get it to run is changing the host.json as follows (although I don’t know what the repercussion would be when deployed … so likely something that should only be done during debugging/development, although I am unsure if this might also affect our workflows running w/ Logic Apps Standard in our Kubernetes environment if they are restarted)

{
  ...
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
    "version": "[1.*, 1.2.18)"
  }
}

As you can see, it seems to be the updated versions of Microsoft.Azure.Functions.ExtensionBundle.Workflows that is causing the issue … if I run it w/ version 1.2.19 it simply freezes and with 2.0.0 specified (which then runs 1.3.7), I get the same issue as you with advapi32.dll

J-Cat on Jan 31, 2023

Hi - this appears to still be happening for me. I’m running in a Dev Container. 1.8.9 is downloaded, and my extension bundle looks like this after removing the above workaround:

“extensionBundle”: { “id”: “Microsoft.Azure.Functions.ExtensionBundle.Workflows”, “version”: “[1.*, 2.0.0)” }

However, I’m still getting the following error:

Value cannot be null. (Parameter ‘provider’) [2023-04-03T07:31:34.377Z] Host unavailable after check. Returning error. 7:34:48 AM: Error: connect ECONNREFUSED 127.0.0.1:8000

HLChucky on Apr 3, 2023