Article ID: 2708922 - View products that this article applies to.
When deploying templates to create new virtual machines (VMs) using System Center Virtual Machine Manager 2008 (VMM), you may receive the following error in the VMM Admin Console:
Boot Configuration Data (BCD) WMI provider is not installed on the Virtual Machine Manager Server.
Install the BCD WMI provider on %ServerName; and then try the operation again.
You also notice that the deployment of VMs fails for all hosts and that the failure also happens for most other templates.
A VMM Trace will show results similar to:
00025010 11:18:35 AM  at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(ManagementException me)
00025011 11:18:35 AM  at Microsoft.Carmine.WMIWrappers.WMIObject.GetMethodParameters(String methodName)
00025012 11:18:35 AM  at Microsoft.Carmine.WMIWrappers.BcdStore.OpenStore(ManagementScope mgmtScope, String File, BcdStore& Store)
00025013 11:18:35 AM  at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store..ctor(WSManConnectionParameters connParams, String storePath)
00025014 11:18:35 AM  *** Carmine error was: HostAgentWMIFail (3154); HR: 0x80131501
00025015 11:18:35 AM  1778.0994::02/04-19:18:35.468#16:BcdUtil.cs(1248):
00025016 11:18:35 AM  1778.0994::02/04-19:18:35.468#16:BcdUtil.cs(1248): Microsoft.VirtualManager.Engine.VmOperations.BCD.BCDWmiProviderNotInstalledException: Error in the application.
00025017 11:18:35 AM  at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store.HandleEx(WSManProviderException wpe)
00025018 11:18:35 AM  at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store..ctor(WSManConnectionParameters connParams, String storePath)
00025019 11:18:35 AM  at Microsoft.VirtualManager.Engine.VmOperations.BCD.BCDFixup.ReadBootManager()
00025020 11:18:35 AM  at Microsoft.VirtualManager.Engine.VmOperations.BCD.BCDFixup..ctor(String bcdFileDir, String bcdFileName, WSManConnectionParameters tgtConnectionParameters, String tgtDevice, UpdateDeploymentCheckpointDelegate checkpointDelegate)
00025021 11:18:35 AM  *** Carmine error was: BcdWmiProviderNotInstalled (13204); 0
This can occur if there is WMI corruption on the VMM server. Examining the local WMI Control properties displays the following:
· Win32_processor: WMI: Invalid namespace
· Win32_WMISetting: WMI: Invalid namespace
· Win32_OperatingSystem: WMI: Invalid namespace
To resolve this issue, rebuild WMI on the VMM server.
Below are the steps to fix the issue on Windows Server 2008:
1. Open an elevated command prompt.
2. Verify the WMI repository is not corrupt by running the following command:
If the repository is not corrupted, a “WMI Repository is consistent” message will be returned. If you get something else, go to step 3. If the repository is consistent, perform a repair.
3. Run the following commands to repair WMI:
If the repository salvage fails to work, then run the following command to see if it resolves the issue:
After the last command, there should be a “WMI Repository has been reset” message returned that verifies the command was successful.
Below are the steps to fix the issue on Windows Server 2003:
1. Stop WMI service
2. From an elevated command prompt run the following:
3. Re-register dlls by running the following command:
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
4. Re-register provider host by running the following command:
5. Re-register WMI service by running the following command:
6. Restart the WMI service
7. Recompile the mofs by running the following command:
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
NOTE For Windows Vista, Windows Server 2008 and all later versions, do not run the command above. In those versions, the uninstall MOF files are now stored in the \wbem directory. Instead, allow WMI auto-recovery to dynamically re-compile MOF files. For applications that do not register for auto-recovery, manually compile their MOF files. You can find a list of auto-recovery MOF files by going to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Wbem\CIMOM registry key and checking the Autorecover MOFs value.
8. Restart the WMI service
9. Restart the VMM server
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2708922 - Last Review: April 11, 2013 - Revision: 4.2