Can't open designer after latest release

[leighchilcott]

Describe the Bug with repro steps

The VSCode designer for Logic App (Standard ) worked completely fine on the previously release, however it is now reporting errors. Several colleagues have the same issue.

1. Right click on workflow.json
2. Open with designer

4:53:58 PM: Azure Logic Apps Standard Runtime Dependencies validation and installation completed successfully. [2023-12-21T16:53:58.492Z] Error configuring services in an external startup class. [2023-12-21T16:53:58.492Z] Error configuring services in an external startup class. Microsoft.Azure.Workflows.WebJobs.Extensions: Could not load type 'Microsoft.Azure.WebJobs.Host.Listeners.IListenerDecorator' from assembly 'Microsoft.Azure.WebJobs.Host, Version=3.0.37.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. [2023-12-21T16:53:58.550Z] A host error has occurred during startup operation '8f52183b-e61b-410d-b494-7cceeca17da0'. [2023-12-21T16:53:58.550Z] Microsoft.Azure.WebJobs.Script: Error configuring services in an external startup class. Microsoft.Azure.Workflows.WebJobs.Extensions: Could not load type 'Microsoft.Azure.WebJobs.Host.Listeners.IListenerDecorator' from assembly 'Microsoft.Azure.WebJobs.Host, Version=3.0.37.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Value cannot be null. (Parameter 'provider') [2023-12-21T16:53:58.568Z] Host startup operation has been canceled [2023-12-21T16:53:58.593Z] Azure Storage connection string is empty or invalid. Unable to write diagnostic events.

Attempted the resolution under https://github.com/Azure/LogicAppsUX/issues/3888 but no change.

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

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": {},
        "parameters": {}
    },
    "kind": "Stateful"
}

Screenshots or Videos

Browser

Chrome, Edge, Firefox

Additional context

No response

[ccastrotrejo]

Hi @leighchilcott thanks for raising this issue. Does this only happen with the latest release? (v2.86.5) It does look like it might be something related to the back end.

Could you please execute the following command in your terminal?func host start --verbose --port "port number you are using" and let me know what is the result of it? This command initializes the design time api and the --verbose prop will help us to have a better idea on what is going on. Thanks!

[leighchilcott]

Hey @ccastrotrejo

Rolling back to a previous version of the extension also gives the same errors as shown above, however a couple of days ago this was absolutely fine.

Running that command I get the following, but then nothing else from the terminal:

PS [Redacted]> func host start --verbose --port 8000
MSBuild version 17.6.1+8ffc3fe3d for .NET
  Determining projects to restore...
  All projects are up-to-date for restore.
C:\Program Files\dotnet\sdk\7.0.302\Current\SolutionFile\ImportAfter\Microsoft.NET.Sdk.Solution.targets(36,5): warning NETSDK1194: The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds. [[Redacted].sln]
  [Redacted] -> [Redacted].dll

Build succeeded.

C:\Program Files\dotnet\sdk\7.0.302\Current\SolutionFile\ImportAfter\Microsoft.NET.Sdk.Solution.targets(36,5): warning NETSDK1194: The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds. [[Redacted].sln]
    1 Warning(s)
    0 Error(s)

Time Elapsed 00:00:23.71

                  %%%%%%
                 %%%%%%
            @   %%%%%%    @
          @@   %%%%%%      @@
       @@@    %%%%%%%%%%%    @@@
     @@      %%%%%%%%%%        @@
       @@         %%%%       @@
         @@      %%%       @@
           @@    %%      @@
                %%
                %

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

[2023-12-22T09:55:24.070Z] Found [Redacted].csproj. Using for user secrets file configuration.
[2023-12-22T09:55:30.681Z] Host lock lease acquired by instance ID '00000000000000000000000045B00C31'.

[phastings389]

hi @ccastrotrejo I am also experiencing the exact same problem since yesterday 22/12/23. It happened since the latest release of Azure Logic Apps (Standard) extension v2.86.5

Even though I rolled back to v2.81.5 , I restarted machine, I have uninstalled and reinstalled Azure Functions Core Tools v. 4.0.5455 but Visual Studio Code is giving me the same error as @leighchilcott - both when trying to open the workflow designer, or when trying to create a data map using the data mapper:

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

[2023-12-22T15:00:32.571Z] Error configuring services in an external startup class. [2023-12-22T15:00:32.571Z] Error configuring services in an external startup class. Microsoft.Azure.Workflows.WebJobs.Extensions: Could not load type 'Microsoft.Azure.WebJobs.Host.Listeners.IListenerDecorator' from assembly 'Microsoft.Azure.WebJobs.Host, Version=3.0.37.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. [2023-12-22T15:00:32.619Z] A host error has occurred during startup operation '07701869-117a-4df2-abdc-fa32dc37e048'. [2023-12-22T15:00:32.619Z] Microsoft.Azure.WebJobs.Script: Error configuring services in an external startup class. Microsoft.Azure.Workflows.WebJobs.Extensions: Could not load type 'Microsoft.Azure.WebJobs.Host.Listeners.IListenerDecorator' from assembly 'Microsoft.Azure.WebJobs.Host, Version=3.0.37.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. Value cannot be null. (Parameter 'provider') [2023-12-22T15:00:32.650Z] Host startup operation has been canceled [2023-12-22T15:00:32.678Z] Azure Storage connection string is empty or invalid. Unable to write diagnostic events. 3:30:17 PM: Error: connect ECONNREFUSED 127.0.0.1:8000

[prorook]

Same issue, started recently. Designer worked about a week ago, reverting to previous versions of standard logic apps extension didn't help.

--verbose func host start: https://pastebin.com/t0pSvLTP

[ccastrotrejo]

Hi all, thank you so much for sending the information with the verbose. It does seem to be a BE issue. I will transfer the issue and start an internal thread with the team, so they can be aware of it and start working on the fix.

In the meantime, as a workaround can you update your host.json extension bundle version from the default [1.*, 2.0..0) to [1.44.16]? This will download and use an older bundle to rule out regression. Please provide the same logs if this works or doesn't work when starting the host.

[prorook]

That seems to be doing the trick for now. Getting a connection refused when trying to grab verbose logs, probably due to it already running on my default port. I'm new here, sorry :)

Successful output when opening designer: Local binary .NET SDK version 6.0.417 6:25:31 PM: Azure Logic Apps Standard Runtime Dependencies validation and installation completed successfully. 6:26:07 PM: Running command: "C:\Users\Admin99b3a29128.azurelogicapps\dependencies\FuncCoreTools\func host start --port 8001" with pid: "688"...

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

Functions:

NetFxLanguageWorkerFunction: NetFxTrigger

XsltNetFxLanguageWorkerFunction: NetFxTrigger

For detailed output, run func with --verbose flag. [2023-12-22T18:26:11.978Z] Worker process started and initialized.

[apranaseth]

Hi, The latest workflow bundle extension needs latest functions core tools version 4.0.5455 or newer, runtime version greater than v4.27. Please install the latest functions core tools.

[mark-abrams]

I had the same issue and upgrading the Functions core tools also fixed it for ne, just as @apranaseth advises.