locked
Error checking stamp information: while registering ASDK to Azure RRS feed

  • Question

  • Hi,

    I was on the last step of executing the PS script:

    $AzureContext = Get-AzureRmContext
    $CloudAdminCred = Get-Credential -UserName AZURESTACK\CloudAdmin -Message "Enter the cloud domain credentials to access the privileged endpoint"
    Set-AzsRegistration `
        -CloudAdminCredential $CloudAdminCred `
        -PrivilegedEndpoint AzS-ERCS01 `
        -BillingModel Development

    I get the pop up sign in window and all, but then, the script craps out with the error:

    2018-01-26.02-22-17: Initializing session with privileged endpoint: AzS-ERCS01. Attempt 0 of 3
    2018-01-26.02-22-52: Connection to AzS-ERCS01 successful
    2018-01-26.02-25-28: Verifying stamp version.
    2018-01-26.02-27-05: ************************ Error ************************
    2018-01-26.02-27-05: An error occurred checking stamp information:
    Exception calling "GetResult" with "0" argument(s): "A WebException occurred while sending a RestRequest. WebException.Status: ConnectFailure."
    2018-01-26.02-27-05:
    2018-01-26.02-27-05: *********************** Ending registration action during Confirm-StampVersion ***********************

    Not sure if this has any effect, but we have a Web proxy. I couldn't find any info online on this, what could be going wrong?

    TIA.

    Friday, January 26, 2018 8:07 PM

Answers

  • Hello Tia,

    That first command needs to be run on the disconnected ASDK Host.

    There is also a is a typo in the first line of the command.  

      

    This returns an error

    $FilePathForRegistrationToken = $env:SystemDrive\RegistrationToken.txt

     

      

    This returns the value: c:\RegistrationToken.txt

    $FilePathForRegistrationToken = "$env:SystemDrive\RegistrationToken.txt"

        

     

    Hope that helps

    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

    Friday, February 2, 2018 2:01 AM

All replies

  • Hello Tia,

    We’ve seen this issue when:

    -ASDK is behind a Web Proxy

    -TCP Port 443 Filter by Firewall

    -Incorrect network configuration on Azs-BGPNAT01

     

    Please validate your connectivity via TCP port 443 to login.windows.net before attempting to register for Marketplace Syndication. 

     

    If you are behind a web proxy and unable to successfully connect to login.windows.net,

    You can still register and download marketplace items in offline mode:

    See: Disconnected registration

         

    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

    Saturday, January 27, 2018 2:25 AM
  • Thanks Gary.

    I have tried the disconnected option as suggested and got:

    PS C:\AzureStack-Tools-master\Registration>
    PS C:\AzureStack-Tools-master\Registration> $FilePathForRegistrationToken = $env:SystemDrive\RegistrationToken.txt
    At line:1 char:49
    + ... FilePathForRegistrationToken = $env:SystemDrive\RegistrationToken.txt
    +                                                    ~~~~~~~~~~~~~~~~~~~~~~
    Unexpected token '\RegistrationToken.txt' in expression or statement.
        + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
        + FullyQualifiedErrorId : UnexpectedToken

    PS C:\AzureStack-Tools-master\Registration>
    PS C:\AzureStack-Tools-master\Registration> echo $FilePathForRegistrationToken
    PS C:\AzureStack-Tools-master\Registration>
    PS C:\AzureStack-Tools-master\Registration> echo $env
    PS C:\AzureStack-Tools-master\Registration>

    Where is command supposed to be run? 

    TIA

    Tuesday, January 30, 2018 9:44 PM
  • Hello Tia,

    That first command needs to be run on the disconnected ASDK Host.

    There is also a is a typo in the first line of the command.  

      

    This returns an error

    $FilePathForRegistrationToken = $env:SystemDrive\RegistrationToken.txt

     

      

    This returns the value: c:\RegistrationToken.txt

    $FilePathForRegistrationToken = "$env:SystemDrive\RegistrationToken.txt"

        

     

    Hope that helps

    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

    Friday, February 2, 2018 2:01 AM
  • Hi Gary,

    For the disconnexted mode, what is the AgreementNumber and where do I get its value from? It is showing as '<your agreement number>' in the PS command. Thank you!

    Tuesday, February 6, 2018 10:14 PM
  • Gary, further update: I removed the AgreementNumber and was able to register to Azure in a disconnected mode, so just as I declaring victory, I saw a new problem.

    When I went to "Marketplace Management" and tried to add from Azure, the button is greyed out. My registration with Azure was successful, as per the command I have executed:

    Register-AzsEnvironment -RegistrationToken $registrationToken

    <snip>

        "Location":  "Global",
        "SubscriptionId":  "xxxxxxxxxxxxx",
        "Properties":  {
                           "cloudId":  "xxxxxxxxxxxx",
                           "billingModel":  "Development"
                       },
        "ETag":  "\"xxxxxxxxxxxxxxxxx\”"
    }
    VERBOSE: 2018-02-07.12-18-52: Your Azure Stack environment is now registered with Azure.
    VERBOSE: 2018-02-07.12-18-52: *********************** End log: Register-AzsEnvironment ***********************

    What do you suggest I do to make this work? WE do use a web proxy (we use that for everything and it works) so I don't believe it is a proxy problem. I was able to wget https://login.windows.net:443 without any problem. I am not sure how else to troubleshoot this issue, any help will be appreciated. Thank you.



    • Edited by Man Solo Wednesday, February 7, 2018 5:51 PM
    Wednesday, February 7, 2018 5:50 PM
  • Hi Gary:

    can you please suggest any correction I can make to get unblocked. It is still saying that I have ASDK successfully registerd to Azure but the "Add from Azure" is greyed out on the portal. Thank you.

    Tuesday, February 13, 2018 5:11 AM
  • This has been taken care here: https://social.msdn.microsoft.com/Forums/azure/en-US/b7e2e58c-0d89-435b-be4f-18eb849b6bf3/add-from-azure-greyed-out?forum=AzureStack#d755be24-4ce5-4970-adcd-67d77cbb95e3  

    Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.

    Thursday, February 22, 2018 8:03 PM