Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Update Rollup 7 for Microsoft Azure Site Recovery Provider


View products that this article applies to.

Introduction

This article describes the fixes that are included in Update Rollup 7 (version 5.1.1186) 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.

↑ Back to the top


Summary

Update Rollup 7 for Microsoft Azure Site Recovery Provider applies to all systems that have Windows Azure Hyper-V Recovery Manager Provider version 5.1.1000 or an earlier version 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)


↑ Back to the top


Issues that are fixed in this update

After you apply this update, the following issues are fixed:
  • When you try to enable protection of a virtual machine, you receive the following error message:
    Protection couldn't be enabled for the virtual machine.

    Provider error: Virtual Machine Manager is unable to retrieve previously stored password information.
    Either restore the key data from a previous backup or enter the information again. (Provider error code: 636)

    (Error code: 70094)
    Possible causes: Protection can't be enabled with the virtual machine in its current state. Check the Provider errors for more information.
    Recommendation: Fix any issues in the Event Viewer logs (Applications and Service Logs - MicrosoftAzureRecoveryServices) on the Hyper-V host server. If this virtual machine is enabled for replication on the Hyper-V host, disable this setting. Then try to enable protection again.


  • Test failover of a virtual machine is unsuccessful, and you receive the following error message:

    "The virtual machine 'vm_name' couldn't be started. (Error code: 25005) The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server (server_name).

↑ Back to the top


Update information

To resolve these issues, install this update from the Microsoft Download Center.

The following file is available for download from the Microsoft Download Center:


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 Microsoft Azure Hyper-V Recovery Manager Provider (version 3.5.468.0 or a later version), Azure Site Recovery (version 4.6.660 or a later version), or Azure Site Recovery (version 5.1.1000 or later) installed. 

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.

↑ Back to the top


Status

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

↑ Back to the top


References

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

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbnotautohotfix, kbfix, kbexpertiseinter, kbbug, kb

↑ Back to the top

Article Info
Article ID : 3096032
Revision : 1
Created on : 1/7/2017
Published on : 10/1/2015
Exists online : False
Views : 407