locked
Azure Stack Dev Kit 1910 installation error RRS feed

  • Question

  • Hi Technical experts:

    I had some trouble installing asdk and I was unable to proceed.

    ---------------------------------------------------------------------------------------------

    Type 'Configure' of Role 'POC' raised an exception:

    DSC failures:
    WIN-15J836O8RT2: One or more partial configurations failed to apply. No configuration could be created.  LCM failed to start desired state configuration manually.

    at PublishAndStartDscConfiguration, C:\CloudDeployment\Common\Helpers.psm1: line 1796
    at Configure, C:\CloudDeployment\Classes\POC\POC.psm1: line 137
    at <ScriptBlock>, <No file>: line 42
    at <ScriptBlock>, <No file>: line 40 - 3/10/2020 6:15:05 PM
    VERBOSE: Step: Status of step '0.PhysicalMachineAndInitialConfiguration.13 - (DEP) Configure Physical Machines networking for POC' is 'Error'. - 3/10/2020 6:15:05 PM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress: '0.PhysicalMachineAndInitialConfiguration.13'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. Finish running all steps that are currently in progress before exiting. - 3/10/2020 6:15:05 PM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just completed: '0.PhysicalMachineAndInitialConfiguration.13'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment-Phase0-DeployBareMetal' failed. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Status of 'Deployment-Phase0-DeployBareMetal' is 'Error'. - 3/10/2020 6:15:05 PM
    COMPLETE: Task Cloud - Deployment-Phase0-DeployBareMetal
    VERBOSE: Task: Status of action 'Deployment-Phase0-DeployBareMetal' of role 'Cloud' is 'Error'. - 3/10/2020 6:15:05 PM
    VERBOSE: Step: Status of step '0.PhysicalMachineAndInitialConfiguration - Phase 0 - Configure physical machine and external networking' is 'Error'. - 3/10/2020 6:15:05 PM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress: '0.PhysicalMachineAndInitialConfiguration'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment-InitialSteps' failed. Finish running all steps that are currently in progress before exiting. - 3/10/2020 6:15:05 PM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just completed: '0.PhysicalMachineAndInitialConfiguration'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment-InitialSteps' failed. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Status of 'Deployment-InitialSteps' is 'Error'. - 3/10/2020 6:15:05 PM
    COMPLETE: Task Cloud - Deployment-InitialSteps
    VERBOSE: Task: Status of action 'Deployment-InitialSteps' of role 'Cloud' is 'Error'. - 3/10/2020 6:15:05 PM
    VERBOSE: Step: Status of step '0 - Initial dependency-based steps' is 'Error'. - 3/10/2020 6:15:05 PM
    VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently in progress: '0'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment' failed. Finish running all steps that are currently in progress before exiting. - 3/10/2020 6:15:05 PM
    VERBOSE: Draining all steps that are still in progress. The following steps are still in progress or just completed: '0'. - 3/10/2020 6:15:05 PM
    VERBOSE: Action: Action plan 'Deployment' failed. - 3/10/2020 6:15:05 PM

    DumpType     : 1
    PSPath       : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
    PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
    PSChildName  : LocalDumps
    PSDrive      : HKLM
    PSProvider   : Microsoft.PowerShell.Core\Registry

    DumpCount    : 1
    PSPath       : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps
    PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
    PSChildName  : LocalDumps
    PSDrive      : HKLM
    PSProvider   : Microsoft.PowerShell.Core\Registry

    Invoke-EceAction : Type 'Configure' of Role 'POC' raised an exception:
    DSC failures:
    WIN-15J836O8RT2: One or more partial configurations failed to apply. No configuration could be created.  LCM failed to start desired state configuration manually.
    at PublishAndStartDscConfiguration, C:\CloudDeployment\Common\Helpers.psm1: line 1796
    at Configure, C:\CloudDeployment\Classes\POC\POC.psm1: line 137
    at <ScriptBlock>, <No file>: line 42
    at <ScriptBlock>, <No file>: line 40
    At C:\CloudDeployment\Setup\Common\DeploySingleNodeCommon.ps1:770 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $ActionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (DSC failures:
    ...ion manually.
    :String) [Invoke-EceAction], InterfaceInvocationFailedException
        + FullyQualifiedErrorId : DSC failures:
    WIN-15J836O8RT2: One or more partial configurations failed to apply. No configuration could be created.  LCM failed to start desired state configuration manually.
    ,CloudEngine.Cmdlets.InvokeCmdlet

    Invoke-EceAction : Action: Invocation of step 0.PhysicalMachineAndInitialConfiguration.13 failed. Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\Common\DeploySingleNodeCommon.ps1:770 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $ActionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Invoke-EceAction : Action: Invocation of step 0.PhysicalMachineAndInitialConfiguration failed. Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\Common\DeploySingleNodeCommon.ps1:770 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $ActionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    Invoke-EceAction : Action: Invocation of step 0 failed. Stopping invocation of action plan.
    At C:\CloudDeployment\Setup\Common\DeploySingleNodeCommon.ps1:770 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $ActionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    --------------------------------------------------------------------------------------------------------------------------

    My hosts's configures is list: (from asdk-prechecker.ps1) 

    [ 21:07:29 ]  -- Check physical disks passed successfully. Note that ASDK handles situations where there is a pre-existing storage pool, and will delete/recreate it.
    [ 21:07:29 ] Checking Memory...
    [ 21:07:29 ]  -- Memory on this server = 128
    [ 21:07:29 ]  -- System memory check passed successfully. ASDK requires a minimum of 96 GB of RAM, with 128 GB recommended.
    [ 21:07:29 ] Checking processor information...
    [ 21:07:31 ]  -- Number of CPU sockets = 2
    [ 21:07:31 ]  -- Number of physical cores =  24
    [ 21:07:31 ]  -- CPU socket count (2) and core count (12) meet the minimum requirements for ASDK.
    [ 21:07:31 ] Checking Hyper-V support on the host...
    [ 21:07:32 ]  -- Hyper-V is already installed. Note that the installer would enable it otherwise.
    [ 21:07:32 ] Checking domain join status...
    [ 21:07:32 ]  -- The host is not domain joined.
    [ 21:07:32 ] Checking Internet access...
    [ 21:07:34 ]  -- This machine has internet access (we tried to contact https://login.windows.net).
    [ 21:07:34 ] Checking Host OS version...
    [ 21:07:34 ]  -- Host OS version: 10.0.17763, SKU: 8
    [ 21:07:34 ]  -- The host OS version matches the requirements for ASDK (10.0.14393).
    [ 21:07:34 ] Checking NIC status...
    [ 21:07:35 ]  -- NIC configuration passed successfully.
    [ 21:07:35 ] Checking NIC requirements...
    ForEach-Object : Cannot validate argument on parameter 'InstanceId'. The argument is null. Provide a valid value for the argument, and then try running the command again.
    At D:\asdk-prechecker.ps1:270 char:37
    +     Get-NetAdapter -IncludeHidden | ForEach-Object {
    +                                     ~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidData: (:) [ForEach-Object], ParameterBindingValidationException
        + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.ForEachObjectCommand

    But, when i running this script on the host before booting in the provider VHDX file, everything is OK.

    who can help me to solve this problem? thanks


    Tuesday, March 10, 2020 1:55 PM

Answers

  • Hi

    I have solved this problem. it seems like my network adapter couldn't support Hyper-V, when i change the adapter, the process start create Hyper-V adapter and continue. 

    My disk is all SSD: 240G OS + 12* 240G data.

    I also change the disk is online ( original is offline), So I don't know which reason  caused the problem..

    One is that all data must be online while VHDX;

    Another is that my network adapter is not supported.

    Intel(R) Ethernet Connection X722 for 1GbE is not supported.

    Intel(R) Ethernet Converged Network Adapter X710 is supported.

    Wednesday, March 11, 2020 9:40 AM

All replies

  • The ASDK Prechecker is supposed to be run from the Base OS, and the error you got is expected when running from the .VHDX. 

    DSC errors that I have seen in the past have been difficult to resolve. To start, try 2 different things:

    1) try to rerun the installation. Some DSC errors are due to operations taking too long, and in many cases a rerun will get past the errors. 

    2) Try a reinstall of the ASDK. You will need to delete the .VHDX from the base OS and download it again. I know this is a pain to re-download the entire thing, but it has resolved these errors in the past. 

    Are you using HDDs or SSDs?

    Wednesday, March 11, 2020 4:22 AM
  • Hi

    I have solved this problem. it seems like my network adapter couldn't support Hyper-V, when i change the adapter, the process start create Hyper-V adapter and continue. 

    My disk is all SSD: 240G OS + 12* 240G data.

    I also change the disk is online ( original is offline), So I don't know which reason  caused the problem..

    One is that all data must be online while VHDX;

    Another is that my network adapter is not supported.

    Intel(R) Ethernet Connection X722 for 1GbE is not supported.

    Intel(R) Ethernet Converged Network Adapter X710 is supported.

    Wednesday, March 11, 2020 9:40 AM