Tuesday 5 November 2013

The first (of many) errors - Failed to inject a ConfigMgr driver into the mounted WIM file Status code=2147749889

The first error! Hopefully this helps someone out..

So, I was working away on our SCCM 2007 R3 infrastructure, which I'm in the process of migrating to SCCM 2012 SP1.

I've set up the migration jobs, which seemed to go swimmingly - that is until they hit the boot images..

The migration job failed with the following error message:

Failed to inject a ConfigMgr driver into the mounted WIM file
The ConfigMgr Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
{
Description = "Failed to insert OSD binaries into the WIM file";
ErrorCode = 2152205056;
File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4262;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"<PACKAGEIDREPLACED>\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
};


I searched the above and found the following link:

http://www.itbl0b.com/2012/02/failed-to-inject-configmgr-driver-into.html#.Unlue4f293A

This article explains exactly what is the issue ( the driver path ( since being imported into CM )has changed), but doesn't go into detail on how to troubleshoot exactly which drivers have the incorrect path.

If you don't want to spend all day verifying the paths for all your drivers, open C:\windows\logs\dism.log. You can see the specific drivers that are causing you the issues





Open the SCCM console, and OSD>Drivers, find the driver, Properties>Update the path.. Retry update to the WIM, everything works fine!  :)




No comments:

Post a Comment