Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Introduction

This article describes the fixes that are included in Update Rollup 10 (version 5.1.1400) for Microsoft Azure Site Recovery Provider. Learn about the details of the fixes and the prerequisites that should be validated before you install this update.

Summary

Update Rollup 10 for Microsoft Azure Site Recovery Provider applies to all systems that have Windows Azure Hyper-V Recovery Manager Provider version 5.1.1000 or earlier installed. These include the following:

  • Microsoft Azure Site Recovery Provider for System Center Virtual Machine Manager (3.3.x.x)

  • Microsoft Azure Site Recovery Provider for Hyper-V (4.6.x.x)

  • Microsoft Azure Site Recovery Provider (5.1.x.x)



Issues that are fixed in this update

After you apply this update, the following issues are fixed:

  • Azure Site Recovery Provider fails with an "ASR cannot be registered due to an internal error. Run Setup again to register the server" error. If you analyze the DraSetupWizard.log in your %ProgramData%\ASRLogs folder, you will find the following message:

    time:NON-CRITICAL FAILURE: Failed to delete Legacy registration settings hive. Exception System.Exception: Setup was unable to access Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\DRAdapter\Registration registry key in LocalMachine registry hive. Please ensure the key exists and is accessible by the user.


  • Azure Site Recovery Provider registration fails with an internal error. If you analyze the DraSetupWizard.log in your %ProgramData%\ASRLogs folder, you will find a message that resembles the following. Particularly notice that the time listed at the beginning of the line does not match the time shown at the end of the line.


    02:49:03:InnerException.Type: System.Exception, InnerException.Message: {"error":"invalid_client","error_description":"ACS50008: SAML token is invalid.\r\nTrace ID: a51b1082-4f0b-492f-9fda-c08677354c3c\r\nCorrelation
    ID: 7ef613b7-a94e-4def-941c-04fe7bcfc075\r\nTimestamp: 2015-12-30 03:51:25Z"}

Update information

To resolve these issues, download and install the following file from the Microsoft Download Center:

Download Download Update Rollup 10 for Microsoft Azure Site Recovery Provider
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To install this update, you must have one of the following installed:

  • Microsoft Azure Hyper-V Recovery Manager Provider (version 3.5.468.0 or later)

  • Microsoft Azure Site Recovery (version 4.6.660 or later)

  • Microsoft Azure Site Recovery (version 5.1.1000 or later)


Note You can check the installed provider version in the Programs and Features item in Control Panel.

Restart information

You don't have to restart the computer after you apply this update. This update automatically stops the System Center Virtual Machine Manager services.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology that Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×