Answered by:
Error Configuring Azure Site Recovery with SCVMM (Check that WS-Management service is installed and running on server)

Question
-
Hi,
I am trying to configure Azure Site Recovery. The preparations are fine and my SCVMM is available in Azure Site Recovery.
I followed the steps "Prepare Infrastructure" and everything works fine until the step "Associate replication policy"-- Check protection prerequisities --> successful
-- Prepare the server --> successful
-- Prepare configuration prprotection --> failed
The error is:
Error ID
10003•
Error MessageProtection couldn't be configured for cloud/site xxxxxxxxxxxxxxxxxxxxxx.
•
Provider errorProvider error code: 31408
Provider error message:
Failed to fetch the version of Microsoft Azure Recovery Services Agent installed on the Hyper-V host server xxxxxxxxxxxxxxxxxxxxxx. Error: An internal error has occurred trying to contact the xxxxxxxxxxxxxxxxxxxxxx server: : .WinRM: URL: [http://xxxxxxxxxxxxxxxxxxxxxx:5985], Verb: [INVOKE], Method: [GetStringValue], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/StdRegProv]
Check that WS-Management service is installed and running on server xxxxxxxxxxxxxxxxxxxxxx. For more information use the command "winrm helpmsg hresult". If xxxxxxxxxxxxxxxxxxxxxx is a host/library/update server or a PXE server role then ensure that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
Provider error possible causes:
It is possible that Registry provider of WMI is corrupted.Provider error recommended action:
Build the repository using MOF compiler and retry the operation.•
Possible causesOne or more hosts couldn't be prepared. Check the Provider error for more information.
•
RecommendationResolve the issue and retry the operation.
VMM Agents are installed
I cannot find any WMI-Problems on the host
I have an SCVMM with 4 Hosts added
Any ideas?
Thanks so much
Regards
JochenFriday, July 21, 2017 1:30 PM
Answers
-
Run the following commands and retry the operation:
PS C:\Windows\system32> cd wbem
PS C:\Windows\system32\wbem> mofcomp regevent.mof
Microsoft (R) MOF Compiler Version 6.3.9600.16384
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: regevent.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
PS C:\Windows\system32\wbem> $hklm = 2147483650
PS C:\Windows\system32\wbem> $key = "Software\Microsoft\Windows\CurrentVersion\Uninstall\Windows Azure Backup"
PS C:\Windows\system32\wbem> $value = "DisplayVersion"
PS C:\Windows\system32\wbem> $wmi = get-wmiobject -list "StdRegProv" -namespace root\cimv2
PS C:\Windows\system32\wbem> ($wmi.GetStringValue($hklm,$key,$value)).svalue
Output: 2.0.9077.0
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
- Marked as answer by Jochen (MSDN) Wednesday, July 26, 2017 6:14 AM
Tuesday, July 25, 2017 7:18 PM
All replies
-
The VMM server and the portal you connect from should have the right time. You can be in any timezone but the time should be correct according to that time zone.
----------------------------------------------------------------------------------
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.- Proposed as answer by SumanthMarigowda-MSFTMicrosoft employee Friday, July 21, 2017 5:00 PM
- Edited by SumanthMarigowda-MSFTMicrosoft employee Saturday, July 22, 2017 4:59 PM
Friday, July 21, 2017 4:02 PM -
All affected Servers (HyperV-Hosts, SCVMM, Machine from where I access the portal) have exactly the same timeMonday, July 24, 2017 6:03 AM
-
This error may occur if WMI registry broken/corrupted on the server. ASR use the WMI registry provider to get the agent version from the registry.
Run the following PowerShell commands with elevated mode (Run PowerShell as an Administrator) and let us know the output
PS C:\Windows\system32> $hklm = 2147483650
PS C:\Windows\system32> $key = "Software\Microsoft\Windows\CurrentVersion\Uninstall\Windows Azure Backup"
PS C:\Windows\system32> $value = "DisplayVersion"
PS C:\Windows\system32> $wmi = get-wmiobject -list "StdRegProv" -namespace root\cimv2
PS C:\Windows\system32> ($wmi.GetStringValue($hklm,$key,$value)).svalue
Reference:
https://technet.microsoft.com/en-us/library/ff406382.aspx#H27
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
Monday, July 24, 2017 2:23 PM -
Hi. I get the following error on every affectet machine (SCVMM and all Hosts)
PS C:\Windows\System32> $hklm = 2147483650
PS C:\Windows\System32> $key = "Software\Microsoft\Windows\CurrentVersion\Uninstall\Windows Azure Backup"
PS C:\Windows\System32> $value = "DisplayVersion"
PS C:\Windows\System32> $wmi = get-wmiobject -list "StdRegProv" -namespace root\cimv2
PS C:\Windows\System32> ($wmi.GetStringValue($hklm,$key,$value)).svalue
Exception calling "GetStringValue" : "Provider not found "
At line:1 char:1
+ ($wmi.GetStringValue($hklm,$key,$value)).svalue
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : WMIMethodException
PS C:\Windows\System32>Thanks
RegardsJochen
Monday, July 24, 2017 5:24 PM -
Im experiencing the same issue! We started out with Hyper-Hosts as a providers but then we installed VMM. We uninstalled the provider and agent from each host. Then we installed and registered the VMM server and installed just the MARS agent on the host. We get the error when we attempt to associate a replication policy with the VMM cloud. Time is in sync and the hosts are responded in VMM.Tuesday, July 25, 2017 2:46 PM
-
Run the following commands and retry the operation:
PS C:\Windows\system32> cd wbem
PS C:\Windows\system32\wbem> mofcomp regevent.mof
Microsoft (R) MOF Compiler Version 6.3.9600.16384
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: regevent.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!
PS C:\Windows\system32\wbem> $hklm = 2147483650
PS C:\Windows\system32\wbem> $key = "Software\Microsoft\Windows\CurrentVersion\Uninstall\Windows Azure Backup"
PS C:\Windows\system32\wbem> $value = "DisplayVersion"
PS C:\Windows\system32\wbem> $wmi = get-wmiobject -list "StdRegProv" -namespace root\cimv2
PS C:\Windows\system32\wbem> ($wmi.GetStringValue($hklm,$key,$value)).svalue
Output: 2.0.9077.0
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
- Marked as answer by Jochen (MSDN) Wednesday, July 26, 2017 6:14 AM
Tuesday, July 25, 2017 7:18 PM -
Thank you vikranth s. You did it!!!
After mofcomp regevent.mof on all affected machines I was able to finish the configuration successfully.
Thank you very much!!!
Wednesday, July 26, 2017 6:16 AM -
I'm glad to hear that your issue is resolved.
Do click on "Mark as Answer" on the post that helps you, this can be beneficial to other community members.
Wednesday, July 26, 2017 6:21 AM