locked
ASDK POC Installation Failure RRS feed

  • Question

  • Hello All,

    We are doing the implementation of ASDK in a connected mode but the installation is getting failed with the following error

    2018-03-02 14:56:42 Verbose  1> [WAS:Configure] Attempting to acquire a token for resource 'https://adminmanagement.hclvolvopoc.onmicrosoft.com/747b64ee-0e70-45ad-b0da-20ebc89aa247' using a refresh token
    2018-03-02 14:56:42 Verbose  1> [WAS:Configure] POST https://login.windows.net/b6c82233-014e-40b5-a379-69f76cd84af2/oauth2/token?api-version=1.6 with -1-byte payload
    2018-03-02 14:56:42 Verbose  1> [WAS:Configure] received 3362-byte response of content type application/json; charset=utf-8
    2018-03-02 14:56:42 Verbose  1> [WAS:Configure] Calling ARM to check if RBAC assignment already exists... (https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01)
    2018-03-02 14:56:42 Verbose  1> [WAS:Configure] GET https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01 with 0-byte payload
    2018-03-02 14:57:57 Warning  1> [WAS:Configure] Issue trying to get existing RBAC assignments (retrying in 10 seconds): {"error":{"code":"AuthenticationFailed","message":"Authentication failed."}}

    Additional details: {
        "Method":  "GET",
        "ResponseUri":  "https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01",
        "StatusCode":  401,
        "StatusDescription":  "Unauthorized",
        "IsFromCache":  false,
        "LastModified":  "\/Date(1519982877562)\/"
    }
    2018-03-02 14:58:07 Verbose  1> [WAS:Configure] GET https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01 with 0-byte payload
    2018-03-02 14:58:07 Verbose  1> [WAS:Configure] ERROR: An error occurred while trying to make an authenticated API call to Resource Manager: {"error":{"code":"AuthenticationFailed","message":"Authentication failed."}}

    Additional details: {
        "Method":  "GET",
        "ResponseUri":  "https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01",
        "StatusCode":  401,
        "StatusDescription":  "Unauthorized",
        "IsFromCache":  false,
        "LastModified":  "\/Date(1519982887829)\/"
    }
    2018-03-02 14:58:07 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 make an authenticated API call to Resource Manager: {"error":{"code":"AuthenticationFailed","message":"Authentication failed."}}

    Additional details: {
        "Method":  "GET",
        "ResponseUri":  "https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01",
        "StatusCode":  401,
        "StatusDescription":  "Unauthorized",
        "IsFromCache":  false,
        "LastModified":  "\/Date(1519982887829)\/"
    }
    at Grant-AdminSubscriptionAccessToDeploymentApplication, C:\CloudDeployment\Roles\WAS\WAS.psm1: line 1674
    at ConfigureWAS, C:\CloudDeployment\Roles\WAS\WAS.psm1: line 964
    at Configure, C:\CloudDeployment\Classes\WAS\WAS.psm1: line 33
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16
    2018-03-02 14:58:07 Error    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 make an authenticated API call to Resource Manager: {"error":{"code":"AuthenticationFailed","message":"Authentication failed."}}

    Additional details: {
        "Method":  "GET",
        "ResponseUri":  "https://adminmanagement.local.azurestack.external/subscriptions/4c5e73ac-6ed8-486c-a106-5da3b54cf680/providers/Microsoft.Authorization/roleAssignments?api-version=2015-07-01",
        "StatusCode":  401,
        "StatusDescription":  "Unauthorized",
        "IsFromCache":  false,
        "LastModified":  "\/Date(1519982887829)\/"
    }
    at Grant-AdminSubscriptionAccessToDeploymentApplication, C:\CloudDeployment\Roles\WAS\WAS.psm1: line 1674
    at ConfigureWAS, C:\CloudDeployment\Roles\WAS\WAS.psm1: line 964
    at Configure, C:\CloudDeployment\Classes\WAS\WAS.psm1: line 33
    at <ScriptBlock>, <No file>: line 18
    at <ScriptBlock>, <No file>: line 16
    2018-03-02 14:58:07 Verbose  1> Step: Status of step '60.140.142 - (Katal) Configure WAS VMs.' is 'Error'.
    2018-03-02 14:58:07 Verbose  1> Checking if any of the in progress steps are complete. The following steps are currently in progress: '60.140.142'.
    2018-03-02 14:58:07 Verbose  1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' failed. Finish running all steps that are currently in progress before exiting.
    2018-03-02 14:58:07 Verbose  1> Draining all steps that are still in progress. The following steps are still in progress or just completed: '60.140.142'.
    2018-03-02 14:58:07 Verbose  1> Action: Action plan 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' failed.
    2018-03-02 14:58:07 Error    1> Action: Invocation of step 60.140.142 failed. Stopping invocation of action plan.
    2018-03-02 14:58:07 Verbose  1> Action: Status of 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' is 'Error'.
    2018-03-02 14:58:07 Verbose  1> Task: Status of action 'Deployment-Phase5-ConfigureWASAndCreateStorageAccounts' of role 'Cloud' is 'Error'.
    2018-03-02 14:58:07 Verbose  Step: Status of step '60.140 - Phase 5 - DeployServices' is 'Error'.
    2018-03-02 14:58:07 Verbose  Checking if any of the in progress steps are complete. The following steps are currently in progress: '60.140'.
    2018-03-02 14:58:07 Verbose  Action: Action plan 'Deployment-Phase2-ConfigureStack' failed. Finish running all steps that are currently in progress before exiting.
    2018-03-02 14:58:07 Verbose  Draining all steps that are still in progress. The following steps are still in progress or just completed: '60.140'.
    2018-03-02 14:58:07 Verbose  Action: Action plan 'Deployment-Phase2-ConfigureStack' failed.
    2018-03-02 14:58:07 Error    Action: Invocation of step 60.140 failed. Stopping invocation of action plan.
    2018-03-02 14:58:07 Verbose  Action: Status of 'Deployment-Phase2-ConfigureStack' is 'Error'.
    2018-03-02 14:58:07 Verbose  Task: Status of action 'Deployment-Phase2-ConfigureStack' of role 'Cloud' is 'Error'.
    2018-03-02 14:58:07 Verbose  Step: Status of step '60 - Phase 2 - ConfigureVMs' is 'Error'.
    2018-03-02 14:58:07 Verbose  Checking if any of the in progress steps are complete. The following steps are currently in progress: '60'.
    2018-03-02 14:58:07 Verbose  Action: Action plan 'Deployment' failed. Finish running all steps that are currently in progress before exiting.
    2018-03-02 14:58:07 Verbose  Draining all steps that are still in progress. The following steps are still in progress or just completed: '60'.
    2018-03-02 14:58:07 Verbose  Action: Action plan 'Deployment' failed.
    2018-03-02 14:58:07 Error    Action: Invocation of step 60 failed. Stopping invocation of action plan.


    Thanking You Bins

    Monday, March 5, 2018 7:20 AM

Answers

All replies

  • Hi Bins,

    Can you check two things?  1. Make sure that the Azure AD account you are using is configured as a Global Administrator for the Azure AD tenant you are using to provide authentication for the ASDK.  Secondly, make sure that the ASDK is able to connect to https://login.windows.net in order to get an authentication token.  Let me know if that helps.

    -Ned

    Monday, March 5, 2018 10:08 PM
  • Global Administrator Role is there

    In addition to that the login is already working as we are having direct internet access on the POC Host as well as the BGPNAT VM.  Please help. 


    Thanking You Bins


    Tuesday, March 6, 2018 3:04 AM
  • Hello,

    Have you tried re-running the deployment? Does it fail in the same place?

      

    In the log you posted, he first error thrown is ‘Unauthorized’.  

    Can you check the ‘Sign Ins’ and ‘Audit Logs’ for your hclvolvopoc.onmicrosoft.com tenant directory Global Administrator and see if it logged the specific authentication error?

     

    Let us know how it goes.

     

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

    If you experience any issues with Azure Stack or the current ASDK release, please feel free to contact us.

           

     Thanks


    Gary Gallanes

    Tuesday, March 6, 2018 7:52 PM
  • I have created a fresh Live ID and activated "Trial subscription" on the same and created a tenant id within the same and retried the installation from scratch. Still facing the same error. 

    I have logged in the Azure Portal and found the following.

    Sign-ins is throwing an error "Something went wrong. Please retry." 

    But in the audit log I am able to see te logs but no errors as such. All are authenticated sessions.



    Thanking You Bins

    Wednesday, March 7, 2018 9:13 AM
  • Hello,

    Is the Azure Portal or Azure Stack Admin Portal throwing the error "Something went wrong. Please retry." ?


    Gary Gallanes

    Saturday, March 10, 2018 2:16 AM