locked
Azure Stack TP3 - Invocation of step 60.61.101 failed on MAS-SQL01 RRS feed

  • Question

  • Hey Guys,

    I did a fresh TP3 installation multiple times and its always failing at step 60.61.101 on MAS-SQL01... :(

    The rerun option stops also at the same step/error and didn't continue.

    VERBOSE: 1> 6> Task: Running interface 'Deployment' of role 'Cloud\Fabric\SQL'. Attempt #1.  -
    3/3/2017 2:33:58 PM
    STARTING: Task Cloud\Fabric\SQL - Deployment
    VERBOSE: 1> 6> Interface: Path to module: C:\CloudDeployment\Classes\SQL\SQL.psm1 - 3/3/2017
    2:33:58 PM
    VERBOSE: 1> 6> Interface: Running interface Deployment (Classes\SQL\SQL.psm1, SQL:Deployment) -
    3/3/2017 2:33:58 PM
    VERBOSE: 1> 6> Execution start of New-Sql. - 3/3/2017 2:34:03 PM
    WARNING: 1> 6> The cluster by the name 'MAS-SqlCl' already exists. - 3/3/2017 2:34:04 PM
    VERBOSE: 1> 6> Skipping: Nodes 'MAS-Sql01' are already part of Cluster 'MAS-SqlCl'. - 3/3/2017
    2:34:04 PM
    VERBOSE: 1> 6> Cluster 'Cluster Network 1' with nodes 'MAS-Sql01'. - 3/3/2017 2:36:04 PM
    VERBOSE: 1> 6> Setting SQL stage to Prepare. - 3/3/2017 2:36:04 PM
    VERBOSE: 1> 6> Execution start of Set-SqlStage. - 3/3/2017 2:36:04 PM
    VERBOSE: 1> 6> Passing the following parameters: - 3/3/2017 2:36:07 PM
    VERBOSE: 1> 6> Creating remote powershell session on MAS-Sql01 - 3/3/2017 2:36:07 PM
    VERBOSE: 1> 6> Initializing remote powershell session on MAS-Sql01 with common functions. -
    3/3/2017 2:36:07 PM
    VERBOSE: 1> 6> Loading infra vm helpers (C:\CloudDeployment\Common\InfraVmHelpers.ps1) to session
    on MAS-Sql01 - 3/3/2017 2:36:07 PM
    VERBOSE: 1> 6> Invoking command on remote session... - 3/3/2017 2:36:07 PM
    VERBOSE: 1> 6> Removing remote powershell session on MAS-Sql01. - 3/3/2017 2:36:11 PM
    WARNING: 1> 6> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL' failed:
    
    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:
    
    Cannot find drive. A drive with the name 'D' does not exist.
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 321
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 111
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9 - 3/3/2017 2:36:11 PM
    Invoke-EceAction : 1> 6> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL'
    failed:
    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:
    Cannot find drive. A drive with the name 'D' does not exist.
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 321
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 111
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9 - 3/3/2017 2:36:11 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (D:String) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.JoinPathCommand,CloudEn
       gine.Cmdlets.InvokeCmdlet
    
    VERBOSE: 1> 6> Step: Status of step '60.61.101 - (FBI) Setup SQL VMs' is 'Error'. - 3/3/2017
    2:36:11 PM
    Invoke-EceAction : 1> 6> Action: Invocation of step 60.61.101 failed. Stopping invocation of
    action plan. - 3/3/2017 2:36:11 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
    
    VERBOSE: 1> 6> Action: Status of 'Deployment-Phase3-DeploySQL' is 'Error'. - 3/3/2017 2:36:11 PM
    COMPLETE: Task Cloud - Deployment-Phase3-DeploySQL
    VERBOSE: 1> 6> Task: Status of action 'Deployment-Phase3-DeploySQL' of role 'Cloud' is 'Error'. -
    3/3/2017 2:36:11 PM
    VERBOSE: 1> Step: Status of step '60.61 - Phase 3 - ConfigureVMs-Part1' is 'Error'. - 3/3/2017
    2:36:11 PM
    Invoke-EceAction : 1> Action: Invocation of step 60.61 failed. Stopping invocation of action
    plan. - 3/3/2017 2:36:11 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet
    
    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 3/3/2017 2:36:11 PM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    - 3/3/2017 2:36:11 PM
    VERBOSE: Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'. - 3/3/2017 2:36:11 PM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. -
    3/3/2017 2:36:11 PM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:526 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet


    From the Deployment logfile I got this:

    2017-03-03 14:33:58 Verbose  1> 6> Task: Running interface 'Deployment' of role 'Cloud\Fabric\SQL'. Attempt #1. 
    2017-03-03 14:33:58 Verbose  1> 6> Interface: Path to module: C:\CloudDeployment\Classes\SQL\SQL.psm1
    2017-03-03 14:33:58 Verbose  1> 6> Interface: Running interface Deployment (Classes\SQL\SQL.psm1, SQL:Deployment)
    2017-03-03 14:34:03 Verbose  1> 6> Execution start of New-Sql.
    2017-03-03 14:34:04 Warning  1> 6> The cluster by the name 'MAS-SqlCl' already exists.
    2017-03-03 14:34:04 Verbose  1> 6> Skipping: Nodes 'MAS-Sql01' are already part of Cluster 'MAS-SqlCl'.
    2017-03-03 14:36:04 Verbose  1> 6> Cluster 'Cluster Network 1' with nodes 'MAS-Sql01'.
    2017-03-03 14:36:04 Verbose  1> 6> Setting SQL stage to Prepare.
    2017-03-03 14:36:04 Verbose  1> 6> Execution start of Set-SqlStage.
    2017-03-03 14:36:07 Verbose  1> 6> Passing the following parameters:
    2017-03-03 14:36:07 Verbose  1> 6> Creating remote powershell session on MAS-Sql01
    2017-03-03 14:36:07 Verbose  1> 6> Initializing remote powershell session on MAS-Sql01 with common functions.
    2017-03-03 14:36:07 Verbose  1> 6> Loading infra vm helpers (C:\CloudDeployment\Common\InfraVmHelpers.ps1) to session on MAS-Sql01
    2017-03-03 14:36:07 Verbose  1> 6> Invoking command on remote session...
    2017-03-03 14:36:11 Verbose  1> 6> Removing remote powershell session on MAS-Sql01.
    2017-03-03 14:36:11 Warning  1> 6> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL' failed: 
    
    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:
    
    Cannot find drive. A drive with the name 'D' does not exist.
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 321
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 111
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9
    2017-03-03 14:36:11 Error    1> 6> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL' failed: 
    
    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:
    
    Cannot find drive. A drive with the name 'D' does not exist.
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 321
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 111
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9
    2017-03-03 14:36:11 Verbose  1> 6> Step: Status of step '60.61.101 - (FBI) Setup SQL VMs' is 'Error'.
    2017-03-03 14:36:11 Error    1> 6> Action: Invocation of step 60.61.101 failed. Stopping invocation of action plan.
    2017-03-03 14:36:11 Verbose  1> 6> Action: Status of 'Deployment-Phase3-DeploySQL' is 'Error'.
    2017-03-03 14:36:11 Verbose  1> 6> Task: Status of action 'Deployment-Phase3-DeploySQL' of role 'Cloud' is 'Error'.

    I did some research on this but the necessary 'D' drive with FileSystemLabel 'Deployment' and also the nuget package 'Solutions.MAS.SQL' are available on MAS-SQL01... strange thing.

    Any Advice?

    Thanks and Regards

    Sascha

    Friday, March 3, 2017 3:00 PM

Answers

  • Can you please confirm that the host machine has a D drive?  Typically if you are booting from VHD the VHD becomes the C drive and the underlying drive hosting the VHD becomes D.  The join path error is trying to create a path from where it is executing, not the target.  If the host machine does not have a D drive or that is assigned to an CD/DVD with nothing inserted then this may be causing the issue.  You can try changing drive assignments on the host such that there is a volume mounted to D.  Note that the full path does not have to be there, it is constructing the path and PowerShell simply needs a volume mounted on D.  This is something that will be addressed in later releases.

    Thanks,

    -Steve


    Steve Linehan | Principal Program Manager | Microsoft Enterprise Cloud Group


    Saturday, March 4, 2017 5:34 PM

All replies

  • Hello Sascha,

    We are investigating your issue: “Invocation of step 60.61.101 failed” and will reply ASAP.

    We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

    Thanks,


    Gary Gallanes

    Friday, March 3, 2017 4:22 PM
  • Hello,

    Before redeploying again using the -rerun parameter:

    -          -  Go to Administrative Tools \ Failover Cluster Manager \ S-Cluster \ Roles  

    -        -   Right click the MAS-SQL01 VM \ More actions \ Reset

    -        -   Allow 3 minutes for all service to start redeploying using the -rerun parameter

    NOTE: Make sure you are running the deployment as under the AzureStack\AzureStackAdmin account.

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

    Thanks,


    Gary Gallanes

    Friday, March 3, 2017 4:49 PM
  • I have the same problem and I already try for 4 times including with your solution but nothing works. The installation is stucking at 60.61.101 step (SQL virtual machine).

    Can you help us?

    Best Regards

    Saturday, March 4, 2017 11:57 AM
  • Can you please confirm that the host machine has a D drive?  Typically if you are booting from VHD the VHD becomes the C drive and the underlying drive hosting the VHD becomes D.  The join path error is trying to create a path from where it is executing, not the target.  If the host machine does not have a D drive or that is assigned to an CD/DVD with nothing inserted then this may be causing the issue.  You can try changing drive assignments on the host such that there is a volume mounted to D.  Note that the full path does not have to be there, it is constructing the path and PowerShell simply needs a volume mounted on D.  This is something that will be addressed in later releases.

    Thanks,

    -Steve


    Steve Linehan | Principal Program Manager | Microsoft Enterprise Cloud Group


    Saturday, March 4, 2017 5:34 PM
  • I was having the same issue and can confirm that reassigning a drive to use 'D' on the host system resolved the problem.  Given that this is a known issue and the variance on hardware people will be testing with, this should be listed on the prerequisites, troubleshooting, and/or known issues pages.

    Technical Specialist, Microsoft


    • Edited by NathanR Saturday, March 4, 2017 8:13 PM
    Saturday, March 4, 2017 8:12 PM
  • Are you doing a visualized install or not using boot from VHD ? This one took me a night .... after attaching a D Drive, it went past SET-SQLServer ...,

    Monday, March 6, 2017 7:39 AM
  • I had the same issue.  The original OS drive changed to G after the initial reboot to the cloudbuilder vhdx.  Its not clear from the post what drive needs to be D, but you would think its the original OS drive that has a number of files.  That couldn't be changed (parameter incorrect from Disk Mgmt when you try to change drive letters), I'm guessing b/c the vhdx was located on the drive.  I started over from scratch and this time after the host rebooted to load cloudbuilder.vhdx the original host drive was D.  No idea why it came up as G during the first install attempt.
    Monday, March 27, 2017 9:26 PM
  • Hello,

    Before redeploying again using the -rerun parameter:

    -          -  Go to Administrative Tools \ Failover Cluster Manager \ S-Cluster \ Roles  

    -        -   Right click the MAS-SQL01 VM \ More actions \ Reset

    -        -   Allow 3 minutes for all service to start redeploying using the -rerun parameter

    NOTE: Make sure you are running the deployment as under the AzureStack\AzureStackAdmin account.

    cd C:\CloudDeployment\setup

    .\InstallAzureStackPOC.ps1 -rerun

    Thanks,


    Gary Gallanes

    Hi Gary ,

    I followed your suggestion , but still got below error and also I checked the D drive is mounted already which is the original C drive before mount the CloudDeployment.vhdx .

    Error I got

    #####################

    VERBOSE: 1> 5> Execution success of Set-SqlStage. - 4/21/2017 4:40:41 AM
    VERBOSE: 1> 5> Setting SQL stage to Complete. - 4/21/2017 4:40:41 AM
    VERBOSE: 1> 5> Setting SQL stage to Complete for node MAS-Sql01. - 4/21/2017 4:40:41 AM
    VERBOSE: 1> 5> Execution start of Set-SqlStage. - 4/21/2017 4:40:41 AM
    VERBOSE: 1> 5> Passing the following parameters: - 4/21/2017 4:40:44 AM
    VERBOSE: 1> 5> Creating remote powershell session on MAS-Sql01 - 4/21/2017 4:40:44 AM
    VERBOSE: 1> 5> Initializing remote powershell session on MAS-Sql01 with common functions. - 4/21/2017 4:40:44 AM
    VERBOSE: 1> 5> Loading infra vm helpers (C:\CloudDeployment\Common\InfraVmHelpers.ps1) to session on MAS-Sql01 - 4/21/2017 4:40:44 AM
    VERBOSE: 1> 5> Invoking command on remote session... - 4/21/2017 4:40:44 AM
    VERBOSE: 1> 5> Removing remote powershell session on MAS-Sql01. - 4/21/2017 4:40:49 AM
    VERBOSE: 1> 5> Executing Set-SqlServer with following arguments: sqlsvcaccount = System.Management.Automation.PSCredential; erroraction =
    Stop; sourcePath = D:\Solutions.MAS.SQL.1.0.1602.24000\content\Setup; sqlsetupstage = Complete; reportfilepath =
    C:\MocsLogs\Sql_Complete_MAS-Sql01.xml; sqlinstancesdata =
    MASSqlWAP:SQL:\\SU1FileServer\SU1_Infrastructure_1\SqlDataBase\SqlShDataWAP:MAS-WAP-HA:IPv4;192.168.200.79;Cluster Network
    1;255.255.255.0:AzureStackAdmin,AzureStack\SqlSvc,AzureStack\FabricAdmin:Sql;  - 4/21/2017 4:40:49 AM
    VERBOSE: 1> 5> Execute Set-SqlServer as scheduled task on node MAS-Sql01. - 4/21/2017 4:40:49 AM
    VERBOSE: 1> 5> Waiting for the scheduled tasks to finish. - 4/21/2017 4:40:49 AM
    WARNING: 1> 5> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL' failed:

    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:

    SQL instance 'MASSqlWAP' Failed on MAS-Sql01 with Error: The following error occurred: Value cannot be null. Parameter name: path2  Error
    result: -2147467261 Result facility code: 0 Result error code: 16387  Please review the summary.txt log for further details Microsoft (R) SQL
     Server 2014 12.00.2000.08  Copyright (c) Microsoft Corporation.  All rights reserved.  . Check file C:\MocsLogs\Sql_Complete_MAS-Sql01.xml
    on Node MAS-Sql01
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 441
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 138
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9 - 4/21/2017 4:41:31 AM
    Invoke-EceAction : 1> 5> Task: Invocation of interface 'Deployment' of role 'Cloud\Fabric\SQL' failed:
    Function 'SQL:Deployment' in module 'Classes\SQL\SQL.psm1' raised an exception:
    SQL instance 'MASSqlWAP' Failed on MAS-Sql01 with Error: The following error occurred: Value cannot be null. Parameter name: path2  Error
    result: -2147467261 Result facility code: 0 Result error code: 16387  Please review the summary.txt log for further details Microsoft (R)
    SQL Server 2014 12.00.2000.08  Copyright (c) Microsoft Corporation.  All rights reserved.  . Check file
    C:\MocsLogs\Sql_Complete_MAS-Sql01.xml on Node MAS-Sql01
    at Set-SqlStage, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 441
    at New-Sql, C:\CloudDeployment\Roles\SQL\SQL.psm1: line 138
    at Deployment, C:\CloudDeployment\Classes\SQL\SQL.psm1: line 19
    at <ScriptBlock>, <No file>: line 9 - 4/21/2017 4:41:31 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OperationStopped: (SQL instance 'M... Node MAS-Sql01:PSObject) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : SQL instance 'MASSqlWAP' Failed on MAS-Sql01 with Error: The following error occurred: Value cannot be null. P
       arameter name: path2  Error result: -2147467261 Result facility code: 0 Result error code: 16387  Please review the summary.txt log for
      further details Microsoft (R) SQL Server 2014 12.00.2000.08  Copyright (c) Microsoft Corporation.  All rights reserved.  . Check file C:
     \MocsLogs\Sql_Complete_MAS-Sql01.xml on Node MAS-Sql01,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> 5> Step: Status of step '60.61.101 - (FBI) Setup SQL VMs' is 'Error'. - 4/21/2017 4:41:31 AM
    Invoke-EceAction : 1> 5> Action: Invocation of step 60.61.101 failed. Stopping invocation of action plan. - 4/21/2017 4:41:31 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> 5> Action: Status of 'Deployment-Phase3-DeploySQL' is 'Error'. - 4/21/2017 4:41:31 AM
    COMPLETE: Task Cloud - Deployment-Phase3-DeploySQL
    VERBOSE: 1> 5> Task: Status of action 'Deployment-Phase3-DeploySQL' of role 'Cloud' is 'Error'. - 4/21/2017 4:41:31 AM
    VERBOSE: 1> Step: Status of step '60.61 - Phase 3 - ConfigureVMs-Part1' is 'Error'. - 4/21/2017 4:41:31 AM
    Invoke-EceAction : 1> Action: Invocation of step 60.61 failed. Stopping invocation of action plan. - 4/21/2017 4:41:31 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    VERBOSE: 1> Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 4/21/2017 4:41:31 AM
    COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack
    VERBOSE: 1> Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. - 4/21/2017 4:41:31 AM
    VERBOSE: Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'. - 4/21/2017 4:41:31 AM
    Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan. - 4/21/2017 4:41:31 AM
    At C:\CloudDeployment\Setup\DeploySingleNode.ps1:535 char:5
    +     Invoke-EceAction -RolePath $masterRole -ActionType $actionPlan @d ...
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], Exception
        + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet

    PS C:\CloudDeployment\Setup>

    ###########################

    samuchen


    • Edited by samuchen Friday, April 21, 2017 12:16 PM
    Friday, April 21, 2017 12:15 PM