Here's another KB we published this morning. This one talks about an issue where creating an MDT based task sequence fails with An error occurred when loading the task sequence and logs a 0x80041002 error in TaskSequenceProvider.log:
=====
Symptoms
After clicking the Finish button when attempting to create an Microsoft Deployment Toolkit (MDT) task sequence, the task sequence may fail to create with the following error:
An error occurred when loading the task sequence
The TaskSequenceProvider.log may also show errors similar to the following:
Failed to load class properties and qualifiers for class BDD_UsePackage in task sequence. 0x80041002 (2147749890) TaskSequenceProvider 11/18/2010 8:28:12 AM 1204 (0x04B4)
Failed to load node Use Toolkit Package from XML into WMI 0x80041002 (2147749890) TaskSequenceProvider 11/18/2010 8:28:12 AM 1204 (0x04B4)
Failed to load children steps for node "Execute Task Sequence" from XML 0x80041002 (2147749890) TaskSequenceProvider 11/18/2010 8:28:12 AM 1204 (0x04B4)
Failed to load children steps for node "" from XML 0x80041002 (2147749890) TaskSequenceProvider 11/18/2010 8:28:12 AM 1204 (0x04B4)
Failed to load XML for the task sequence into WMI 0x80041002 (2147749890) TaskSequenceProvider 11/18/2010 8:28:12 AM 1204 (0x04B4)
Cause
This error can occur if the MDT WMI classes are not properly registered.
Resolution
To resolve this issue follow the steps below:
1. Close all of your remote and local SCCM admin console sessions.
2. Log on to your Configuration Manager server and select Start -> All Programs -> Microsoft Deployment Toolkit -> Configure ConfigMgr Integration.
3. In the Configure ConfigMgr Integration wizard, select “Remove the ConfigMgr custom action definitions” and then click next to remove all the definitions.
4. Re-run Configure ConfigMgr Integration again, and select “Install the ConfigMgr extensions”
Once you do this try creating the Task Sequence again. It should now complete successfully.
More Information
This error occurs because the BDD_* WMI classes have not been correctly registered under the \root\SMS\site_<sitecode> namespace in WMI.
=====
For the latest version of this article see the link below:
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis
