Windows 10 Upgrade Task Sequence: Software Center can not be loaded. There is a problem loading the required components for Software Center

[surfincow]

Hello,

 

Getting ready to roll out our Windows 7 to Windows 10 upgrade task sequence which has been working great during our testing. However, since the recent upgrade to 1606, users in the pilot are getting the following message when they try to launch the upgrade via Software Center:

 

 

Looking at the logs, I found this SCClient log:

 

<![LOG[Call to ExecuteMethod failed, WMI MethodName "CCM_ProgramsManager", MethodClass "ExecuteProgram", called by (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at ExecuteMethod)]LOG]!><time="12:40:50.8041475" date="8-31-2016" component="SCClient" context="" type="3" thread="7" file="">


<![LOG[Exception caught in ExecuteMethod, line 383, file C:\vso\_work\9\s\DataAbstractionLib\WmiDataProvider\WmiConnectionManager.cs - Type System.Management.ManagementException: Not found (Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager at ExecuteMethod)]LOG]!><time="12:40:50.8071598" date="8-31-2016" component="SCClient" context="" type="3" thread="7" file="">


<![LOG[stackTrace: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, String callerMethodName)]LOG]!><time="12:40:50.8161967" date="8-31-2016" component="SCClient" context="" type="3" thread="7" file="">


<![LOG[unhandled exception was caught. (Microsoft.SoftwareCenter.Client.SingleInstanceApplication at OnGetException)]LOG]!><time="12:40:50.8212172" date="8-31-2016" component="SCClient" context="" type="3" thread="1" file="">


<![LOG[Exception caught in OnGetException, line 170, file C:\vso\_work\9\s\SoftwareCenterApplication\App.cs - Type Microsoft.SoftwareCenter.Client.Data.WmiException: Not found (Microsoft.SoftwareCenter.Client.SingleInstanceApplication at OnGetException)]LOG]!><time="12:40:50.8222213" date="8-31-2016" component="SCClient" context="" type="3" thread="1" file="">


<![LOG[stackTrace: at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at Microsoft.SoftwareCenter.Client.Data.WmiConnectionManager.ExecuteMethod(String methodClass, String methodName, Dictionary`2 methodParameters, String callerMethodName)]LOG]!><time="12:40:50.8222213" date="8-31-2016" component="SCClient" context="" type="3" thread="1" file="">

During the testing pre-1606 upgrade, I personally tested it on multuple VM's and on several different models of notebooks and never received the error. Now though, I've been able to replicate the error a few times and not sure what would be causing it as Software Center appears to be working fine. You can see the different apps/updates/operating system deployments, install applications but when you try the task sequence, it will give the warning about it being an operating system upgrade and that you will lose your data (normal warning) then it gives this message.

 

I've been able to move past this on my test machines by waiting a few minutes and trying again, or when that didn't work running ccmreset.exe. The other testers though arent having much luck so I'm hoping someone here may know what the issue might be. I do notice it references: C:\vso which there is no such directory.

 

CM 1606 on 2012R2 with the 5.00.8412.1007 client on Windows 7 SP1 computers.

 

 

Thanks

[Namoh21]

Were you able to find a solution for this issue? I'm experiencing the same issue and have seem to stump Microsoft.

[anyweb]

hi can you attach the execmgr.log pls

[Namoh21]

I do see this part of the execmgr.log at the time of clicking Install for my OSD:

 

OnOptionalExecutionRequests attempted for package IVP00330 optional program * [QueueRequest: false RunOnCompletion : true QuietMode: true SDKCallerId: (null)] execmgr 10/17/2016 9:36:08 AM 496 (0x01F0)

Validating package IVP00330 program * in the chain. The content request ID is {00000000-0000-0000-0000-000000000000} execmgr 10/17/2016 9:36:08 AM 496 (0x01F0)

Creating an optional execution request for package IVP00330 program * execmgr 10/17/2016 9:36:08 AM 496 (0x01F0)

Content is not available on the DP for this program. The program cannot be run now. execmgr 10/17/2016 9:36:10 AM 496 (0x01F0)

OnOptionalExecutionRequests failed for program * : 0x87d01106 execmgr 10/17/2016 9:36:10 AM 496 (0x01F0)

OR

 

OnOptionalExecutionRequests attempted for package IVP002B9 optional program * [QueueRequest: false RunOnCompletion : true QuietMode: true SDKCallerId: (null)] execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44)

Validating package IVP002B9 program * in the chain. The content request ID is {00000000-0000-0000-0000-000000000000} execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44)

Creating an optional execution request for package IVP002B9 program * execmgr 10/17/2016 9:42:07 AM 3908 (0x0F44)

Content is not available on the DP for this program. The program cannot be run now. execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44)

OnOptionalExecutionRequests failed for program * : 0x87d01106 execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44)

I have validated that the DPs for this client had all the packages that are part of this Task Sequence (which is ID: IVP00330 or IVP002B9, two different tests seen here). I have tested this same Task Sequence with an older SCCM client and the image works. It seems like I cannot install my Windows 10 Task Sequence or Windows 7 while using client 5.00.8412.1307. If I PXE or Media boot the computer, I can image with no issues.

[anyweb]

i've seen this problem before

Content is not available on the DP for this program. The program cannot be run now. execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44)

OnOptionalExecutionRequests failed for program * : 0x87d01106 execmgr 10/17/2016 9:42:09 AM 3908 (0x0F44)

to resolve either redeploy the task sequence (short term, the problem will come back), or reduce the number of deployments targeted at the computer, eg: if the computer is targeted with many updates or task sequences, reduce them drastically, and this is probably true seeing as it's windows 7 (think of the updates...), this is the long term fix

 

lastly it can also mean that the policy for the task sequence hasn't arrived yet (the message is confusing...), and this could be due to waiting for a scehduled restart from another program or windows updates,

 

either way to improve the situation, you must reduce the number of deployments aimed at that computer (or computers)

[Namoh21]

We do not use SCCM for system updates for our windows 7 TS, just our Windows 10. Our Windows 7 TS has been working for years before I did the 1607 upgrade. The only system updates we have deployed to the system is Windows 10 cumulative, Security and Virus Definitions. None of those updates are deployed to a Windows 7 device, as we use a WSUS for Win7. I do not have an option to redeploy the TS to the DP as all the packages are showing as being distributed. I have even rebuilt the DP role on the DP with no luck. I can run the TS when the computer has an older client, so I'm thinking there is an issue with the new SCCM client. Still waiting to hear back from MS on if they have found anything in their code.

[anyweb]

redeploy the ts just means re-create the deployment, not re-distribute the content

[Namoh21]

sorry, early morning for me.

I have redeployed the deployment, Created a new collection and a copy of the TS to make sure there was no "bad data" causing this issue. MS has replied to me today saying this might be an existing bug and they might have a fix to test with. Crossing my fingers on this one.

[anyweb]

ok great, did you notice any difference after re-deploying the task sequence (in execmgr.log on affected computers)

[Namoh21]

no difference to my errors. Per Microsoft, it's a known bug (SMS 448525) and I'm waiting for them to have a solution to the issue.