Helpdesk Dude

PROBLEM TEMPORARILY FIXED: After some Google'ing by our Systems Support Associate in the office as well as emails from other external IT individuals (thanks KLJ for the help) it looks like this is a good reference point for a fix: http://blogs.technet.com/b/configmgrteam/archive/2013/07/17/issues-reported-with-ms13-052-kb2840628-and-configmgr.aspx After we removed the update, imaging magically worked again. Gotta love it when Microsoft breaks their own stuff. Hopefully they will have a fix issued soon. For a few more laughs check this out: http://www.infoworld.com/t/microsoft-windows/3-more-botched-windows-patches-kb-2803821-kb-2840628-and-kb-2821895-222807 Good luck guys!

No unfortunately we have not. One of our systems support folks is likely going to submit a support ticket with Microsoft in the morning. We tried this Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1 (https://support.microsoft.com/kb/2854009/en-us) this afternoon, but after installing it we weren't any further ahead. I know Hyodo mentioned above that they might remove their updates. Hyodo have you had any luck with that?

Yea we haven't done anything as of yet. Our server admin is back in the office tomorrow when I plan to run the idea of removing the updates past him. Hopefully we'll figure something out because I'm going to have to start imaging laptops pretty soon.

As you can see from the list I posted before it was mainly security updates. The ones that would have caused the issue were installed on 7/16. As you can see we hadn't done any updates since May otherwise. I installed a few more updates last night that were available to see if any would fix the damage that had been done (fools wish) and of course no luck.

Windows Internet Explorer 9 for Windows Server 2008 R2 for x64-based Systems Successful Optional 7/18/2013 ISecurity Update for Windows Server 2008 R2 x64 Edition (1<82835361) Successful Important 7/16/2013 Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 forx64 (K82840628) Successful Important 7/16/2013 SecurityUpdateforMicrosoft.NETFramework 3.5.lon Windows 7 and Windows Server2008 R2 SPlforx64-based Systems (1<82840631) Successful Important 7/16/2013 Windows Malicious Software Removal Tool x64 - July 2013 (K88 90830) Successful Important 7/16/2013 Security Update for Windows Server 2008 R2 x64 Edition (K82813430) Successful Important 7/16/2013 Security Update for Windows Server 2008 R2 x64 Edition (1<82834886) Successful Important 7/16/2013 Security Update for Windows Server 2008 R2 x64 Edition (1<82845690) Successful Important 7/16/2013 Security Update for Windows Server 2008 R2 x64 Edition (KB2850851) Successful Important 7/16/2013 Cumulative Security Update for Internet Explorer 8 for Windows Server 2008 R2 x64 Edition (1<82846071) Successful Important 7/16/2013 Update for Windows Server 2008 R2 x64 Edition (KB2834140) Successful Recommended 7/16/2013 Update for Windows Server 2008 R2 x64 Edition (1<82808679) Successful Recommended 7/16/2013 Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SPlforx64-based Systems (1<82833946) Successful Important 7/16/2013 Security Update for Windows Server 2008 R2 x64 Edition (1<82839894) Successful Important 7/16/2013 Security Update for Microsoft ,NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 forx64 (1<82835393) Successful Important 7/16/2013 Security Update for Microsoft Silverlight (K82847559) Successful Important 7/16/2013 SecurityUpdateforMicrosoft.NETFramework 3.5.lon Windows 7 and Windows Server2008 R2 SPlforx64-based Systems (KB2844286) Successful Important 7/16/2013 Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 for x64-based Systems (K82832414) Successful Important 7/16/2013 Update for Windows Server 2008 R? x64 Edition (1<82820331) Successful Recommended 5/31J2013

KLJ, Had you guys recently applied Windows Updates to your server that may have caused imaging to break? Just curious if we can create a correlation on what is going on.

We really don't do a lot with the Application side of SCCM. We have updates deployed through it and we do our machine imaging. I haven't created a custom captured image for a while either as the ones we have uploaded were working fine until now.

We are receiving the exact same error as KLJ is reporting. Everything has been running fine until Tuesday night (July 16th) when our server admin ran Windows Updates on our SCCM 2012 SP1 box (Server 2008 R2 Standard with SP1) and we have been receiving an immediate task sequence failure ("An error occurred while resolving dependencies for the selected task sequence (0x80004005)") upon imaging our laptops (Dell's, HP's, Lenovo's). Below is the log off of one of our Lenovo/IBM T60p laptops: <![LOG[reply from server is 'NoReply']LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="libsmsmessaging.cpp:2048"> <![LOG[DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,3489)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="libsmsmessaging.cpp:3489"> <![LOG[ContentLocations.RequestContentLocations(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9281)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="libsmsmessaging.cpp:9281"> <![LOG[content location request failed]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="libsmsmessaging.cpp:9281"> <![LOG[CCM::SMSMessaging::GetContentLocationEx( pszPackageID, pszPackageType, lSourceVersion, pszSiteCode, pszServer, pTransport, pszClientGUID, NULL, true, NULL, bIsClientOnInternet ? true : false, lSMSCLRList ), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2021)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="resolvesource.cpp:2021"> <![LOG[Content location request failed for P0100003:2. (Code 0x80004005)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="resolvesource.cpp:2021"> <![LOG[FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,1863)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="tspolicy.cpp:1863"> <![LOG[Content location request for P0100003:2 failed. (Code 0x80004005)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="tspolicy.cpp:1863"> <![LOG[hr, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2626)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="tspolicy.cpp:2626"> <![LOG[Failed to resolve PackageID=]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="tspolicy.cpp:2626"> <![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,3412)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="tspolicy.cpp:3412"> <![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1523)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="tsmediawizardcontrol.cpp:1523"> <![LOG[Failed to resolve selected task sequence dependencies. Code(0x80004005)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="tsmediawizardcontrol.cpp:1523"> <![LOG[hrReturn, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="320" file="tsmediaresolveprogresspage.cpp:445"> <![LOG[ThreadToResolveAndExecuteTaskSequence failed. Code(0x80004005)]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="3" thread="320" file="tsmediaresolveprogresspage.cpp:445"> <![LOG[ThreadToResolveAndExecuteTaskSequence returned code 0x80004005]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="1" thread="576" file="tsmediaresolveprogresspage.cpp:221"> <![LOG[setting wizard error: An error occurred while resolving dependencies for the selected task sequence (0x80004005). For more information, contact your system administrator or helpdesk operator.]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="576" file="tsmediawizardcontrol.cpp:1547"> <![LOG[ResolveProgressPage::OnWizardNext()]LOG]!><time="15:04:40.368+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="576" file="tsmediaresolveprogresspage.cpp:113"> <![LOG[Activating Finish Page.]LOG]!><time="15:04:40.384+300" date="07-18-2013" component="TSPxe" context="" type="0" thread="576" file="tsmediafinishpage.cpp:107"> <![LOG[Loading bitmap]LOG]!><time="15:04:40.384+300" date="07-18-2013" component="TSPxe" context="" type="1" thread="576" file="tsmbootstrap.cpp:1228"> <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="15:04:42.471+300" date="07-18-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:857"> <![LOG[The command completed successfully.]LOG]!><time="15:04:42.471+300" date="07-18-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:939"> <![LOG[successfully launched command shell.]LOG]!><time="15:04:42.471+300" date="07-18-2013" component="TSBootShell" context="" type="1" thread="784" file="bootshell.cpp:430"> Any thoughts on the matter would be greatly appreciated.