We are stuck with this error while installing ASR provider and registering with Azure Vault, can i get some help on this

Error:

NO Vaults could be retried for the registration key. Please ensure that
1, your registration key has not expired.You can re-downloading registration key from Azure site Recovery portal
2, Your system clock is not out of sync with the selected system time zone

System Clock is set to IST and Azure to southeastasia

Hi,

Could you please ensure that you have downloaded the latest registration key from the portal?

Also ensure that the machine from where you are accessing the portal and the VMM server has the right time according to your time zone.

Thank you,

Ruturaj

Thanks for the reply Ruturaj.

1, Yes the Registration Key is the latest, we  tried out with 2 different subscription but the same error.

2, The VMM server time Zone is IST India and the vault is set to East Asia and i connected to the portal from the VMM server itself.

Any other criteria to be considered.

Thank you,

Leo 

Hi Lecelest, is the problem still appearing? Kindly file a support case in case it is not yet resolved.

Thank you,

Ruturaj

Hi Lecelest,

I have exactly the same problem, my GMT zone is (UTC) London, Lisbon and Azure Site Recovery created in Western Europe. What did you do to solve the problem?

---------------------------
Microsoft Azure Site Recovery Provider Setup
---------------------------
No vaults could be retrieved for Registration key. Please ensure that :
1) Your Registration key has not expired. You can try re-downloading Registration key from Azure Site Recovery portal.
2) Your system clock is not out of sync with the selected system time zone.

Hi,

I tried to download the file using powershell script, but get the same ERROR.

Add-AzureAccount
Select-AzureSubscription "MSDN"

$Vault = Get-AzureSiteRecoveryVault -Name "DemoVault"
Get-AzureSiteRecoveryVaultSettingsFile -Vault $Vault

Best Regards,

Can you please share the logs from %Programdata%\VMMLogs\DRALogs folder.

Regards,

Anoop KV

I put the logs in OneDrive https://onedrive.live.com/redir?resid=889CFB0AC77A4A10%21165921

thanks for the help.

Best regards,

Moreira

 Hi Anoop KV,

at the moment only the log after the error: :)

2015-07-22T17:19:20.0193365+00:00 Always: Trace Session Started
05:19:20:
05:19:20:Application Started
05:19:20:Main : Current directory = D:\3ca9625159917fca00c496f398
05:19:20:Setup action value = UserInterface
05:19:20:DRSetup Version 3.5.785.0
05:19:20:Work flow option Repair
05:19:20:Adding Page LaunchPage
05:19:20:Enter Microsoft.VirtualManager.DRA.Setup.LaunchPage
05:19:20:Adding Page WelcomePage
05:19:20:Adding Page MicrosoftUpdatePage
05:19:20:Adding Page InstallationPage
05:19:20:Adding Page InstallationSummaryPage
05:19:20:Adding Page RegistrationInformationPage
05:19:20:Adding Page WelcomeUpgradePage
05:19:20:Adding Page WelcomeUninstallPage
05:19:20:Adding Page UninstallationPage
05:19:20:Adding Page UninstallationSummaryPage
05:19:20:Starting Register from C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin\DRConfigurator.exe
05:19:20:
2015-07-22T17:19:20.1287368+00:00 Always: Trace Session Ended
2015-07-22T17:19:20.1912123+00:00 Always: Trace Session Started
05:19:20:
05:19:20:Application Started
05:19:20:Main : Current directory = D:\3ca9625159917fca00c496f398
05:19:20:Proxy not specified
05:19:20:VMM Friendly name was not specified
05:19:20:Credential file was not specified
05:19:20:KEK was not specified.
05:19:20:Channel integrity key was not specified
05:19:20:Pre-Req Checks will be run
05:19:20:Normal register
e-register mode
05:19:20:Setup action value = UserInterface
05:19:20:Work flow option Register
05:19:20:Adding Page LaunchPage
05:19:20:Enter Microsoft.VirtualManager.DRA.Configurator.LaunchPage
05:19:20:Adding Page PreRegistration
05:19:20:Adding Page WelcomePage
05:19:20:Adding Page ProxyConfigurationPage
05:19:20:Adding Page VMMSettingsPage
05:19:20:Adding Page CloudSettingsPage
05:19:20:Adding Page RegistrationPage
05:19:20:Adding Page RegistrationSummaryPage
05:19:20:Exit Microsoft.VirtualManager.DRA.Configurator.LaunchPage
05:19:20:Enter Microsoft.VirtualManager.DRA.Configurator.WelcomePage
05:19:20:Adding PreReq for E2E replication
05:19:20:Adding new PreReq to list
05:19:20:Adding PreReq to UI for PreReq Support on-premises to on-premises protection
05:19:20:Adding PreReq for E2A replication
05:19:20:Adding new PreReq to list
05:19:20:Adding PreReq to UI for PreReq Support on-premises to Azure protection
05:19:20:Evaluating PreReq Support on-premises to on-premises protection
05:19:20:Executing PreReq eval func E2ESupported
05:19:20:Evaluating PreReq Support on-premises to Azure protection
05:19:20:Executing PreReq eval func E2ASupported
05:19:20:service status Stopped
05:19:20:SCVMM is not running
05:19:20:Updating UI elements after PreReq checks
05:19:20:Starting update of UI for PreReq Support on-premises to on-premises protection
05:19:20:Starting update of UI for PreReq Support on-premises to Azure protection
05:19:20:service status Stopped
05:19:22:service status Stopped
05:19:22:Exit Microsoft.VirtualManager.DRA.Configurator.WelcomePage
05:19:22:Enter Microsoft.VirtualManager.DRA.Configurator.ProxyConfigurationPage
05:19:22:Checking for proxy options. This will happen only once
05:19:22:Checking for Bypass settings
05:19:22:Checking for Default settings
05:19:22:Using webProxy to check internet connectivity
05:19:22:Using default proxy to check internet connectivity
05:19:22:Resetting application proxy settings.
05:19:22:Updating UI elements
05:19:22:Resetting application proxy settings.
05:19:22:Updating UI elements
05:19:24:Exit Microsoft.VirtualManager.DRA.Configurator.ProxyConfigurationPage
05:19:24:Enter Microsoft.VirtualManager.DRA.Configurator.VMMSettingsPage
05:19:29:VMMRegistrationClient called with acsUrl https://wepod01rrp1users.accesscontrol.windows.net/ relyingParty http://windowscloudbackup/m3
05:19:29:Get all service resource claims
05:19:29:Getting all service resource against the certificate with thumbprint: AC343628FA39506A9B8A9D2AB4003D7F132D1947
05:19:29:Getting the claims from ACS
05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}
05:19:30:StackTrace:   at SrsRestApiClientLib.Acs.GetOAuth2ResponseFromAcs(Dictionary`2 requestParameters)
   at SrsRestApiClientLib.Acs.GetTokenFromAcsUsingCert()
   at Microsoft.VirtualManager.DRA.Registration.ACSHelper.GetClaimsFromACSToken()
   at Microsoft.VirtualManager.DRA.Registration.VMMRegistrationClient.GetAllServiceResourceClaims(String certThumbprint)
05:19:30:DRRegistrationException while trying to get all disaster recovery vault for the selected certificate: : Threw Exception.Type: Microsoft.VirtualManager.DRA.Registration.DRRegistrationException, Exception.Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}
05:19:30:StackTrace:   at Microsoft.VirtualManager.DRA.Registration.VMMRegistrationClient.GetAllServiceResourceClaims(String certThumbprint)
   at Microsoft.VirtualManager.DRA.Configurator.RegisterActionProcessor.GetAllServiceResources(String managementCertThumbprint)
05:19:30:InnerException.Type: System.Exception, InnerException.Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}
05:19:30:InnerException.StackTrace:   at SrsRestApiClientLib.Acs.GetOAuth2ResponseFromAcs(Dictionary`2 requestParameters)
   at SrsRestApiClientLib.Acs.GetTokenFromAcsUsingCert()
   at Microsoft.VirtualManager.DRA.Registration.ACSHelper.GetClaimsFromACSToken()
   at Microsoft.VirtualManager.DRA.Registration.VMMRegistrationClient.GetAllServiceResourceClaims(String certThumbprint)
05:19:35:The user canceled setup
05:19:35:Application Ended
05:19:35:Successful
05:19:35:Property Bag Values:
05:19:35:SetupStartTime = 22/07/2015 17:19:20
05:19:35:DefaultLogName = C:\ProgramData\VMMLogs\DRALogs\DRASetupWizard.log
05:19:35:setupexepath = C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\bin
05:19:35:InstallPath = C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\
05:19:35:KekFileName = DataEncryptionCertificate_150722-171920.pfx
05:19:35:KekStatus = NotGenerated
05:19:35:DataEncryptionEnabled = False
05:19:35:SkipPreReqChecks = False
05:19:35:RunConfigurator = False
05:19:35:BypassDefaultProxy = True
05:19:35:ProxyChanged = Bypass
05:19:35:WorkFlow = Register
05:19:35:SyncInitialCloudData = True
05:19:35:ProxyAddress =
05:19:35:ProxyPort =
05:19:35:ProxyUsername =
05:19:35:ManagementCertThumbprint = AC343628FA39506A9B8A9D2AB4003D7F132D1947
05:19:35:AcsUrl = https://wepod01rrp1users.accesscontrol.windows.net/
05:19:35:RelyingPartyScope = http://windowscloudbackup/m3
05:19:35:ChannelIntegrityKey = System.Security.SecureString
05:19:35:ErrorMessage = No vaults could be retrieved for Registration key. Please ensure that :-
1) Your Registration key has not expired. You can try re-downloading Registration key from Azure Site Recovery portal.
2) Your system clock is not out of sync with the selected system time zone.
05:19:35:End of list Property Bag Values.
05:19:35:
2015-07-22T17:19:35.8422794+00:00 Always: Trace Session Ended

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee 1 hour 59 minutes ago

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee 2 hours 3 minutes ago

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee Wednesday, August 19, 2015 5:17 AM

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee Wednesday, August 19, 2015 5:17 AM

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee Wednesday, August 19, 2015 5:17 AM

Thanks for sharing the logs...

05:19:30:Error:GetAllServiceResourceClaims failed with error:  , Exception Type: System.Exception, Exception Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: f6fa9d09-b459-444c-af86-10e1d38f2ae7\r\nCorrelation ID: 4bbea134-44df-40ec-8a41-0a3c3e897a19\r\nTimestamp: 2015-07-22 16:20:55Z"}

the logs clearly shows a difference of almost 13 hours between your machine and the correct time. Can you please double check why this difference?

Regards,

Anooop KV

• Proposed as answer by Anoop KV(MSFT)Microsoft employee Wednesday, August 19, 2015 5:17 AM

Thank you for your quick reply.
I checked this issue, but in reality my current time(UTC) will never be the same of  Microsoft data center in Amsterdam.
It is because of the time diference? The solution is to create the ASR in northern Europe instead of Western Europe?

I will make some tests.

Thank You.

Best Regards,
Moreira

Hi Anoop KV,

I can't solve this problem.
If you check the server starts the log with the correct time, (7/22/2015 T17:19:20.0193365 + 00:00 Always: Trace Session Started), but in the second row the registration is already as 05:19.

The hour mistake only happens with the VMMASRProvider_x64.exe file.

Do you have any idea to work around the problem?

Best Regards,

Moreira

Hi Anoop KV,

Best Regards,

Moreira

Hi Anoop KV,

Tricky problem?

Best Regards,

Moreira

Hello Moreira,

This will require some more in-depth analysis. Can you please start a email thread with me. my email id is anoopkv@Microsoft.com

Regards,

Anoop KV

Thanks Moreiera for contacting us directly. Over our emails conversations we were able to diagnose the issue - the problem was the time on the server was not in sync with the Global Time. We fixed the time on the server and the issue is now resolved.

Regards,

Anoop KV