Azure service fabric cluster creation crashes - Requested value 'PUBLIC' was not found

Trevor Barry 26 Reputation points
2023-01-27T17:34:43.78+00:00

Hi,

Environment:

Windows Server 2022 Datacenter 21H2, up to date with patches, domain joined

SharePoint Subscription Edition, up to date with patches, no prior workflow setup

Logged in a Domain Admin/Local Admin/Farm Admin


I'm trying to setup the new Workflow Manager for SharePoint ([https://www.microsoft.com/en-us/download/confirmation.aspx?id=104867) and the installation instructions specify that I need to create a standalone Azure Service Fabric Cluster from the download here - [https://download.microsoft.com/download/8/3/6/836E3E99-A300-4714-8278-96BC3E8B5528/9.0.1048.9590/Microsoft.Azure.ServiceFabric.WindowsServer.9.0.1048.9590.zip

When I run the service fabric cluster installer with the command

.\CreateServiceFabricCluster.ps1 -ClusterConfigFilePath .\ClusterConfig.Unsecure.DevCluster.json -AcceptEULA -Verbose

it crashes with the message "Requested value 'PUBLIC' was not found."

The verbose output shows a stack trace indicating that the error is in "Microsoft.ServiceFabric.DeploymentManager.BPA.BestPracticesAnalyzer", specifically " at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)"

Digging a bit more indicates that the problem seems to be in Test-ServiceFabricConfiguration.

The SFDeployer log file contains


2023/01/27-17:20:41.486,Info,11028,SystemFabricDeployer.SFDeployer,Running Best Practices Analyzer...

2023/01/27-17:20:41.488,Verbose,11028,SystemFabricDeployer.SFDeployer,Validating executing user is an Administrator.

2023/01/27-17:20:41.488,Verbose,11028,SystemFabricDeployer.SFDeployer,Converting JSON config to model.

2023/01/27-17:20:41.604,Info,11028,ImageBuilder.FabricDeployer,Host name: SP-SUBEDITION.

2023/01/27-17:20:41.621,Info,11028,ImageBuilder.FabricDeployer,Network interface ip address: fe80::a9f3:a8f0:676b:afd2%12.

2023/01/27-17:20:41.621,Info,11028,ImageBuilder.FabricDeployer,Network interface ip address: 192.168.0.131.

2023/01/27-17:20:41.625,Info,11028,ImageBuilder.FabricDeployer,Network interface ip address: ::1.

2023/01/27-17:20:41.625,Info,11028,ImageBuilder.FabricDeployer,Network interface ip address: 127.0.0.1.


Any ideas?

It looks like a bug in the service fabric installer code but I can't find any reports of this error.

I've tried other json config files and they all produce the same error.

Thanks

Trevor

Azure Service Fabric
Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
252 questions
{count} vote

2 answers

Sort by: Most helpful
  1. VasimTamboli 4,420 Reputation points
    2023-04-09T07:05:42.6733333+00:00

    It seems that the error "Requested value 'PUBLIC' was not found" occurs when the Service Fabric Cluster creation script is unable to find a value for a particular field in the configuration file. To troubleshoot this issue, you may want to check the JSON configuration file and ensure that all the required fields are populated with the correct values. Here are a few things you can try:

    Check if you have the latest version of the Azure Service Fabric Cluster installer. Download and install the latest version from the official Microsoft website.

    Check the JSON configuration file for any missing or incorrect values. Make sure all required fields are populated and that they contain valid values. You can refer to the official documentation for a list of required fields and their valid values.

    Try using a different JSON configuration file to see if the error persists. You can find sample configuration files in the Service Fabric SDK.

    Check if the Service Fabric Cluster creation script has the necessary permissions to access the required resources. Ensure that the account running the script has sufficient privileges to create the cluster.

    Check if there are any firewall rules that are blocking the script from accessing the resources it needs. You may need to adjust the firewall settings to allow the script to run successfully.

    3 people found this answer helpful.
    0 comments No comments

  2. Trevor Barry 26 Reputation points
    2023-05-03T19:51:21.52+00:00

    If anybody is still following this -

    In my case the problem was caused by in incorrect IPv6 DNS server entry on the SP server. The entry wasn't causing any other problems.

    Once I deleted that the install worked :-)

    Thanks to Microsoft for helping me get to the bottom of this.

    Trevor

    0 comments No comments