Run SUM tool failed. Stack Trace: at Initialize-SBECauRunOnNode

Question

Run SUM tool failed. Stack Trace: at Initialize-SBECauRunOnNode

TI Admin chibhoua 5

Hello,

Deploying a single node HPE 380 gen11, with OS v 2509, does anyone had this issue?

Type 'SBEPartnerInitializeCAURunOnNode' of Role 'SBE' raised an exception: SBE_HPE_ProLiant-Standard_4.2.2509.10: SBEPartnerInitializeCAURunOnNode failed to complete extension interface Initialize-SBECauRunOnNode on node 'XXX.XXX.XX.XX': Error running Initialize-SBECauRunOnNode. Error: Run SUM tool failed. Stack Trace: at Initialize-SBECauRunOnNode,

HC,

Thank you

Anonymous

2025-11-01T00:15:43.09+00:00
Hi TI Admin chibhoua

Thank you for reaching out Q/A. Based on the error you have shared this issue can occur due to one of two known scenarios:

Scenario 1: Incorrect SBE Family Installed

There are two SBE family types provided by HPE:

HPE_ProLiant-Standard – intended for Integrated System platforms.

HPE_ProLiant-Minimal – intended for non-integrated or single-node systems.

If the wrong family is installed the SBE initialization will fail.

In this case, cleanup is required before retrying the update. Please perform the following steps:

Identifying and deleting the relevant action plan instances to clear the stuck update state.

Delete each action plan instance blocking the update process, ensuring the update service no longer treats the update as in progress.

Remove the local SBE cache directories associated with the incorrect SBE installation version to clear residual data.

Scenario 2: HPE iLO Security Mode Configuration

If your iLO is configured in High Security Mode, the SUM tool execution will fail with the same error message.

To resolve this:

Log in to the HPE iLO interface.

Navigate to Security → Encryption tab.

Change the Security Mode from High Security to Production.

Allow iLO to restart.

Repeat the same on all nodes.

Once completed, please retry the installation and let us know the outcome so we can confirm resolution or proceed with further analysis.
Anonymous

2025-11-03T15:58:48.61+00:00

Hi @TI Admin chibhoua

Could you please confirm, if above provided information was helpful! Please let us know if the issue persists after applying these steps.
TI Admin chibhoua 5 Reputation points

2025-11-07T18:10:17.9733333+00:00

Hi Jilakara,

Thanks for the answer, I already tried without any success,
Anonymous

2025-11-07T21:37:15.83+00:00

Thanks for the update. @TI Admin chibhoua

I’ve shared the next steps and validation commands with you in a private message. Kindly review and let me know once checked. If you have any questions while going through it, feel free to update.

Looking forward to your response.

Anonymous

Hi @TI Admin chibhoua

Could you please confirm, if you have performed below mitigations only?

If you have already had an actionplan please note. If you don't have to find the action plan

SQL

$client = Create-ECEClientSimple
$client.GetActionPlanInstances() | Select Name, Status, ActionPlanInstanceId, CreationTime

Once you have the ActionPlanInstances IDs you can fill them into this mitigation script and run from any cluster node

# use the ActionPlanInstanceID values from the query in prior step
$actionIDs = @("", "", "") # Replace with actual ActionPlanInstanceID values
# Create a new ECEClientSimple object to interact with the ECE API
$eceClient = Create-ECEClientSimple
$description = New-Object Microsoft.AzureStack.Solution.Deploy.EnterpriseCloudEngine.Controllers.Models.DeleteActionPlanInstanceDescription
foreach ($id in $actionIDs) {
    Write-Host "Deleting ActionPlan Instance $id"
    $description.ActionPlanInstanceID = $id
    $eceClient.DeleteActionPlanInstance($description)
}
$localCacheDir = [System.Environment]::GetEnvironmentVariable("SBELocalPath", "Machine")
# Adjust the -like value below to assure you got the correct local Cache path associated with the cancelled SBE
if ($localCacheDir -like "*4.1.2411.10") {
    Write-Host "Deleting SBE Cache directory at $localCacheDir"
    Invoke-Command -ComputerName (Get-ClusterNode).Name -ScriptBlock {
        if (Test-Path -Path $using:localCacheDir) {
            Remove-Item -Path $using:localCacheDir -Recurse -Force | Out-Null
        }
    }
}

Your answer

Anonymous

2025-11-01T00:15:43.09+00:00

Hi TI Admin chibhoua

Thank you for reaching out Q/A. Based on the error you have shared this issue can occur due to one of two known scenarios:

Scenario 1: Incorrect SBE Family Installed

There are two SBE family types provided by HPE:

HPE_ProLiant-Standard – intended for Integrated System platforms.

HPE_ProLiant-Minimal – intended for non-integrated or single-node systems.

If the wrong family is installed the SBE initialization will fail.

In this case, cleanup is required before retrying the update. Please perform the following steps:

Identifying and deleting the relevant action plan instances to clear the stuck update state.

Delete each action plan instance blocking the update process, ensuring the update service no longer treats the update as in progress.

Remove the local SBE cache directories associated with the incorrect SBE installation version to clear residual data.

Scenario 2: HPE iLO Security Mode Configuration

If your iLO is configured in High Security Mode, the SUM tool execution will fail with the same error message.

To resolve this:

Log in to the HPE iLO interface.

Navigate to Security → Encryption tab.

Change the Security Mode from High Security to Production.

Allow iLO to restart.

Repeat the same on all nodes.

Once completed, please retry the installation and let us know the outcome so we can confirm resolution or proceed with further analysis.
Anonymous

2025-11-03T15:58:48.61+00:00

Hi @TI Admin chibhoua

Could you please confirm, if above provided information was helpful! Please let us know if the issue persists after applying these steps.
TI Admin chibhoua 5 Reputation points

2025-11-07T18:10:17.9733333+00:00

Hi Jilakara,

Thanks for the answer, I already tried without any success,
Anonymous

2025-11-07T21:37:15.83+00:00

Thanks for the update. @TI Admin chibhoua

I’ve shared the next steps and validation commands with you in a private message. Kindly review and let me know once checked. If you have any questions while going through it, feel free to update.

Looking forward to your response.
Anonymous

2025-11-12T17:11:27.6966667+00:00

Hi @TI Admin chibhoua

Could you please confirm, if you have performed below mitigations only?

If you have already had an actionplan please note. If you don't have to find the action plan

SQL

$client = Create-ECEClientSimple $client.GetActionPlanInstances() | Select Name, Status, ActionPlanInstanceId, CreationTime

Once you have the ActionPlanInstances IDs you can fill them into this mitigation script and run from any cluster node

# use the ActionPlanInstanceID values from the query in prior step $actionIDs = @("", "", "") # Replace with actual ActionPlanInstanceID values # Create a new ECEClientSimple object to interact with the ECE API $eceClient = Create-ECEClientSimple $description = New-Object Microsoft.AzureStack.Solution.Deploy.EnterpriseCloudEngine.Controllers.Models.DeleteActionPlanInstanceDescription foreach ($id in $actionIDs) { Write-Host "Deleting ActionPlan Instance $id" $description.ActionPlanInstanceID = $id $eceClient.DeleteActionPlanInstance($description) } $localCacheDir = [System.Environment]::GetEnvironmentVariable("SBELocalPath", "Machine") # Adjust the -like value below to assure you got the correct local Cache path associated with the cancelled SBE if ($localCacheDir -like "*4.1.2411.10") { Write-Host "Deleting SBE Cache directory at $localCacheDir" Invoke-Command -ComputerName (Get-ClusterNode).Name -ScriptBlock { if (Test-Path -Path $using:localCacheDir) { Remove-Item -Path $using:localCacheDir -Recurse -Force | Out-Null } } }