Share via

ASDK deployment - Invocation of interface 'Configure' of role 'Cloud\Fabric\WAS' failed

AdamOliver-8833 1 Reputation point
2022-09-01T22:11:45.417+00:00

I have twice had the ASDK deployment fail on the Cloud\Fabric\WAS role. The info I found online addressed when it is timing out due to a firewall issue. For me, the server is returning a 404 error, so it appears to be getting to the endpoint. I am trying to deploy this ASDK to an Azure Government tenant. Not sure if I am getting a bad endpoint, or if there is some kind of installer script issue. I already had to alter a script so it would recognize I was using a Global Administrator in the tenant. It seems FederationMetadataEndpoint is coming up as .com when it should be .us. 

VERBOSE: 1> [WAS:Configure] Passing the following parameters: - 9/1/2022 8:36:07 PM  
VERBOSE: 1> [WAS:Configure] [ArgumentList] = [{  
    "GraphVersion":  "1.6",  
    "FederationMetadataEndpoint":  
"https://login.microsoftonline.com/<tenant ID>/federationmetadata/2007-06  
/federationmetadata.xml",  
    "GraphEndpoint":  "https://graph.windows.net/<tenant ID>"  
}] - 9/1/2022 8:36:07 PM  
VERBOSE: 1> [WAS:Configure] Creating remote powershell session on AzS-WAS01 - 9/1/2022 8:36:07 PM  
VERBOSE: 1> [WAS:Configure] Initializing remote powershell session on AzS-WAS01 with common  
functions. - 9/1/2022 8:36:07 PM  
VERBOSE: 1> [WAS:Configure] Loading infra vm helpers  
(C:\CloudDeployment\Common\InfraVmHelpers.psm1) to session on AzS-WAS01 - 9/1/2022 8:36:07 PM  
VERBOSE: 1> [WAS:Configure] Invoking command on remote session... - 9/1/2022 8:36:08 PM  
VERBOSE: 1> [WAS:Configure] ECE PowerShellHost Script End - 9/1/2022 8:36:30 PM  
VERBOSE: 1> Interface: PowerShell job terminal state is Failed for interface 'Configure'. -  
9/1/2022 8:36:30 PM  
VERBOSE: 1> [PSTask Concurrency] [39>WAS:Configure] Exiting throttling instance. Priority '0',  
Weight '10'. - 9/1/2022 8:36:31 PM  
VERBOSE: 1> [PSTask Concurrency] [39>WAS:Configure] Parallel task count decreased by '10' to '0'.  
- 9/1/2022 8:36:31 PM  
WARNING: 1> Task: Invocation of interface 'Configure' of role 'Cloud\Fabric\WAS' failed:  
  
Type 'Configure' of Role 'WAS' raised an exception:  
  
An error occurred while trying to test identity provider endpoints: System.Net.WebException: The  
remote server returned an error: (404) Not Found.  
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)  
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()  
at <ScriptBlock>, <No file>: line 52 - 9/1/2022 8:36:31 PM  
Invoke-EceAction : Type 'Configure' of Role 'WAS' raised an exception:  
An error occurred while trying to test identity provider endpoints: System.Net.WebException: The  
remote server returned an error: (404) Not Found.  
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)  
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()  
at <ScriptBlock>, <No file>: line 52  
At line:5 char:2  
+  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Rerun -Retr ...  
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
    + CategoryInfo          : OperationStopped: (:) [Invoke-EceAction], InterfaceInvocationFailed  
   Exception  
    + FullyQualifiedErrorId : An error occurred while trying to test identity provider endpoints:  
    System.Net.WebException: The remote server returned an error: (404) Not Found.  
   at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)  
       at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord(),CloudEngine.Cmdlets.In  
   vokeCmdlet  
  
VERBOSE: 1> Step: Status of step '60.140.143 - (Katal) Configure WAS VMs.' is 'Error'. - 9/1/2022  
8:36:31 PM  
VERBOSE: 1> Checking if any of the in progress steps are complete. The following steps are  
currently in progress: '60.140.143'. - 9/1/2022 8:36:31 PM  
VERBOSE: 1> Action: Action plan reached terminal state due to one of the steps. Finish running all  
 remaining steps that may still be currently in progress before exiting. - 9/1/2022 8:36:31 PM  
VERBOSE: 1> Draining all steps that are still in progress. The following steps are still in  
progress or just completed: '60.140.143'. - 9/1/2022 8:36:31 PM  
VERBOSE: 1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' failed. -  
 9/1/2022 8:36:31 PM  
Invoke-EceAction : Action: Invocation of step 60.140.143 failed. Stopping invocation of action  
plan.  
At line:5 char:2  
+  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Rerun -Retr ...  
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
    + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException  
    + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet  
  
VERBOSE: 1> Action: Status of 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' is 'Error'.  
 - 9/1/2022 8:36:31 PM  
COMPLETE: Task Cloud - Deployment-Phase5-ConfigureWASAndCreateStorageAccounts  
VERBOSE: 1> Task: Status of action 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' of  
role 'Cloud' is 'Error'. - 9/1/2022 8:36:31 PM  
VERBOSE: Step: Status of step '60.140 - Phase 5 - DeployServices' is 'Error'. - 9/1/2022 8:36:31  
PM  
VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently  
in progress: '60.140'. - 9/1/2022 8:36:31 PM  
VERBOSE: Action: Action plan reached terminal state due to one of the steps. Finish running all  
remaining steps that may still be currently in progress before exiting. - 9/1/2022 8:36:31 PM  
VERBOSE: Draining all steps that are still in progress. The following steps are still in progress  
or just completed: '60.140'. - 9/1/2022 8:36:31 PM  
VERBOSE: Action: Action plan 'Deployment-Phase2-ConfigureStack' failed. - 9/1/2022 8:36:31 PM  
Invoke-EceAction : Action: Invocation of step 60.140 failed. Stopping invocation of action plan.  
At line:5 char:2  
+  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Rerun -Retr ...  
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
    + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException  
    + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet  
  
VERBOSE: Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'. - 9/1/2022 8:36:31 PM  
COMPLETE: Task Cloud - Deployment-Phase2-ConfigureStack  
VERBOSE: Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'. -  
9/1/2022 8:36:31 PM  
VERBOSE: Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'. - 9/1/2022 8:36:31 PM  
VERBOSE: Checking if any of the in progress steps are complete. The following steps are currently  
in progress: '60'. - 9/1/2022 8:36:31 PM  
VERBOSE: Action: Action plan reached terminal state due to one of the steps. Finish running all  
remaining steps that may still be currently in progress before exiting. - 9/1/2022 8:36:31 PM  
VERBOSE: Draining all steps that are still in progress. The following steps are still in progress  
or just completed: '60'. - 9/1/2022 8:36:31 PM  
VERBOSE: Action: Action plan 'Deployment' failed. - 9/1/2022 8:36:31 PM  
Invoke-EceAction : Action: Invocation of step 60 failed. Stopping invocation of action plan.  
At line:5 char:2  
+  Invoke-EceAction -RolePath Cloud -ActionType Deployment -Rerun -Retr ...  
+  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
    + CategoryInfo          : InvalidOperation: (:) [Invoke-EceAction], ActionExecutionException  
    + FullyQualifiedErrorId : Unspecified error,CloudEngine.Cmdlets.InvokeCmdlet  
  
WARNING: Root element is missing.
Azure Stack Hub
Azure Stack Hub
An extension of Azure for running apps in an on-premises environment and delivering Azure services in a datacenter.
189 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. AdamOliver-8833 1 Reputation point
    2022-09-02T13:18:20.467+00:00

    I think this may be a problem with a rerun. When checking logs I noticed a rerun would show the parameters being used that it pulled from before. Not all would show, including that I had selected AzureUSGovernment as the infrastructure. I did a compete redeployment, and this time altered the script to fix the global administrator piece as soon as it was created. This meant it did not fail on that step so I never did a rerun. This morning I woke up to see the deployment created successfully.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.