Forum Discussion
Error No File
I have tried to deploy the Azure Local cluster based on Stack HCI, but are currently stuck on the Creating Cluster portion.
However the fault it gives is very unclear and says there is a network configuration error however All previous steps where succesfull including setting up networking where I assume it would have failed if it was a networking issue. The name of the cluster would be something else if I where to configure it manually but this name comes from Azure and was validated there.
Error:
Type 'ConfigCluster' of Role 'Cluster' raised an exception: Check the spelling of the cluster name. Otherwise, there might be a problem with your network. Make sure the cluster nodes are turned on and connected to the network or contact your network administrator. at SetClusterLiveDumpPolicy, C:\NugetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.10.2507.1001.1000\content\CloudDeployment\Classes\Cluster\Cluster.psm1: line 898 at ConfigCluster, C:\NugetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.10.2507.1001.1000\content\CloudDeployment\Classes\Cluster\Cluster.psm1: line 322 at <ScriptBlock>, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 163 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 158 at <ScriptBlock>, <No file>: line 50
4 Replies
Also now seeing on a 23H3 2504 that is trying to update to 2507:
Description
update ARB VM an d vm extensions on inside of Arb VM
Error details
Type 'UpdateArbAndExtensions' of Role 'MocArb' raised an exception: [UpgradeArbAndExtensions :arcappliance upgrade] Failed with Error C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd arcappliance upgrade hci --config-file "C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\MocArb\WorkingDirectory\Appliance\hci-appliance.yaml" --only-show-errors returned a non empty error stream [ERROR: The command failed with an unexpected error. Here is the traceback: ERROR: [Errno 2] No such file or directory: 'debug_infra.yaml' Traceback (most recent call last): File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 664, in execute File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 731, in _run_jobs_serially File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 701, in _run_job File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 334, in __call__ File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler File "C:\CloudContent\AzCliExtensions\arcappliance\azext_arcappliance\pkg\cliconfig\telemetry_config.py", line 113, in _wrapped_func return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "C:\CloudContent\AzCliExtensions\arcappliance\azext_arcappliance\custom.py", line 1169, in upgrade_appliance_cmd return upgrade_appliance(appliance_client, provider, appliance_config, resource_config, infra_config, no_wait)I have same issue right now on upgraded cluster from 22H2 to 23H2.
I have an active case with Microsoft.
The error you see is because a file required .xml file in the users documents folder has not been created. Basically this file tells the deployment that cloud endpoints can be reached.
I have tried to manually create this file, but then I get an error on access denied.
Microsoft have not provided me with solution yet, but I will post here once I get a solution.Since it is a Test deployment cluster I will whipe all config and retry from scratch
Check this first:
1. Cluster Name Resolution
Even though the name comes from Azure, verify that:
• The cluster name resolves correctly via DNS from all nodes.
• You can ping <cluster-name> from each node.
• Run Resolve-DnsName <cluster-name> to confirm it’s registered.
2. Node Connectivity
Ensure:
• All nodes are powered on and reachable.
• No firewall rules are blocking SMB, RPC, or WinRM between nodes.
• You can run Test-Cluster manually from one node and get a clean result.
3. Live Dump Policy Permissions
The SetClusterLiveDumpPolicy cmdlet may require elevated permissions or specific registry access. Try:
Get-ClusterResource
Get-ClusterGroup
If these fail, the cluster may not have initialized properly.
4. Deployment Logs
Check:
• C:\CloudDeployment\Logs\ClusterCreation.log
• C:\ClusterStorage\Volume1\DeploymentLogs (if applicable)
Look for more specific errors around line 898 in Cluster.psm1.
