KB: Deploying templates to create new VMs using System Center Virtual Machine Manager fails with Error 13204

KB: Deploying templates to create new VMs using System Center Virtual Machine Manager fails with Error 13204

  • Comments 1
  • Likes

image4/11/2013 - NOTE: This article has been updated. Please see http://support.microsoft.com/kb/2708922 for the latest version.

=====

Here’s a new Knowledge Base article we published this morning. This one describes an issue where deploying templates to create new VMs using System Center Virtual Machine Manager fails with Error 13204.

=====

Symptoms

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:

Error 13204
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 [6008] at Microsoft.Carmine.WSManWrappers.ErrorContextParameterHelper.ThrowTranslatedCarmineException(ManagementException me)
00025011 11:18:35 AM [6008] at Microsoft.Carmine.WMIWrappers.WMIObject.GetMethodParameters(String methodName)
00025012 11:18:35 AM [6008] at Microsoft.Carmine.WMIWrappers.BcdStore.OpenStore(ManagementScope mgmtScope, String File, BcdStore& Store)
00025013 11:18:35 AM [6008] at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store..ctor(WSManConnectionParameters connParams, String storePath)
00025014 11:18:35 AM [6008] *** Carmine error was: HostAgentWMIFail (3154); HR: 0x80131501
00025015 11:18:35 AM [6008] 1778.0994::02/04-19:18:35.468#16:BcdUtil.cs(1248):
00025016 11:18:35 AM [6008] 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 [6008] at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store.HandleEx(WSManProviderException wpe)
00025018 11:18:35 AM [6008] at Microsoft.VirtualManager.Engine.VmOperations.BCD.Store..ctor(WSManConnectionParameters connParams, String storePath)
00025019 11:18:35 AM [6008] at Microsoft.VirtualManager.Engine.VmOperations.BCD.BCDFixup.ReadBootManager()
00025020 11:18:35 AM [6008] at Microsoft.VirtualManager.Engine.VmOperations.BCD.BCDFixup..ctor(String bcdFileDir, String bcdFileName, WSManConnectionParameters tgtConnectionParameters, String tgtDevice, UpdateDeploymentCheckpointDelegate checkpointDelegate)
00025021 11:18:35 AM [6008] *** Carmine error was: BcdWmiProviderNotInstalled (13204); 0

Cause

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

Resolution

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:

winmgmt /verifyrepository

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:

winmgmt /salvagerepository

If the repository salvage fails to work, then run the following command to see if it resolves the issue:

winmgmt /resetrepository

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:

cd %windir%\system32\wbem

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:

wmiprvse /regserver

5. Re-register WMI service by running the following command:
winmgmt /regserver

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

8. Restart the WMI service
9. Restart the VMM server

=====

For the most current version of this article please see the following:

2708922 - Deploying templates to create new VMs using System Center Virtual Machine Manager fails with Error 13204

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment