Jump to content


klj

Task Sequence Failure

Recommended Posts

Having problems with task sequece failure. we have gone as far as rebuiling the DP and just uploading what we need to image. Recreated the task sequence and the boot image.

Here is the log file..

 

Any help or suggestions would be great!

 

Content location request: TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Sending RequestContentLocations for KLJ00005 TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Setting message signatures. TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Setting the authenticator. TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
CLibSMSMessageWinHttpTransport::Send: URL: BSMK-SCCM.klj-solutions.com:80 CCM_POST /ccm_system/request TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Request was succesful. TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
reply from server is 'NoReply' TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,3489) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
ContentLocations.RequestContentLocations(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9281) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
content location request failed TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
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) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Content location request failed for KLJ00005:35. (Code 0x80004005) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,1863) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Content location request for KLJ00005:35 failed. (Code 0x80004005) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
hr, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2626) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Failed to resolve PackageID= TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,3412) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
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) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
Failed to resolve selected task sequence dependencies. Code(0x80004005) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
hrReturn, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,445) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
ThreadToResolveAndExecuteTaskSequence failed. Code(0x80004005) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)
ThreadToResolveAndExecuteTaskSequence returned code 0x80004005 TSPxe 7/18/2013 11:03:27 AM 1116 (0x045C)
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. TSPxe 7/18/2013 11:03:27 AM 1116 (0x045C)
ResolveProgressPage::OnWizardNext() TSPxe 7/18/2013 11:03:27 AM 1116 (0x045C)
Activating Finish Page. TSPxe 7/18/2013 11:03:27 AM 1116 (0x045C)
Loading bitmap TSPxe 7/18/2013 11:03:27 AM 1116 (0x045C)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 7/18/2013 11:03:37 AM 852 (0x0354)
The command completed successfully. TSBootShell 7/18/2013 11:03:37 AM 852 (0x0354)
Successfully launched command shell. TSBootShell 7/18/2013 11:03:37 AM 852 (0x0354)

Share this post


Link to post
Share on other sites

have you verified if the 35th version of this package is on the dp ?

 

Content location request failed for KLJ00005:35. (Code 0x80004005) TSPxe 7/18/2013 11:03:27 AM 1272 (0x04F8)

 

 

have you checked that the network access account is all ok ?

have you looked at the distmgr.log file for any clues as to your problem

Share this post


Link to post
Share on other sites

I did verify that all necessary packages are on the DP.

I did verify that the account was good too..

I looked in the distmgr.log and there wasn't any errors in there ... it's weird, this just stopped working. I have also gone in a verified that there wasn't any certificates being blocked and have stripped all drivers out in the package.

 

What dependencies is it looking for?

 

"An error occured resolving dependecies for the selected taske sequence (0x8004005)"

 

From the distmrg.log

 

 

Starting package processing thread, thread ID = 0x470 (1136) SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:32 PM 5724 (0x165C)
Starting package processing thread, thread ID = 0x628 (1576) SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 5724 (0x165C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 5724 (0x165C)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=1136 GMTDATE=Thu Jul 18 17:39:33.431 2013 ISTR0="Configuration Manager Client Package" ISTR1="KLJ00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ00003" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 1136 (0x0470)
No action specified for the package KLJ00003. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 1136 (0x0470)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=1576 GMTDATE=Thu Jul 18 17:39:33.432 2013 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="KLJ00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ00004" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 1576 (0x0628)
No action specified for the package KLJ00004. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:33 PM 1576 (0x0628)
Package KLJ00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
The package and/or program properties for package KLJ00003 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=KLJ00003, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
Package KLJ00004 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
The package and/or program properties for package KLJ00004 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=KLJ00004, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
StoredPkgVersion (1) of package KLJ00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
SourceVersion (1) of package KLJ00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
StoredPkgVersion (1) of package KLJ00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
SourceVersion (1) of package KLJ00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=1136 GMTDATE=Thu Jul 18 17:39:34.525 2013 ISTR0="Configuration Manager Client Package" ISTR1="KLJ00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ00003" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1136 (0x0470)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=1576 GMTDATE=Thu Jul 18 17:39:34.541 2013 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="KLJ00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ00004" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:34 PM 1576 (0x0628)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:37 PM 4692 (0x1254)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:38 PM 5724 (0x165C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:38 PM 5724 (0x165C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:42 PM 4692 (0x1254)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:43 PM 5724 (0x165C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:43 PM 5724 (0x165C)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:48 PM 5724 (0x165C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:39:48 PM 5724 (0x165C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:07 PM 4692 (0x1254)
Found package properties updated notification for package 'KLJ0017D' SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:12 PM 5724 (0x165C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:12 PM 4692 (0x1254)
Found notification for package 'KLJ0017D' SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 5724 (0x165C)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 5724 (0x165C)
Starting package processing thread, thread ID = 0x18B4 (6324) SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 5724 (0x165C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 5724 (0x165C)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=6324 GMTDATE=Thu Jul 18 17:44:17.913 2013 ISTR0="Test Motha" ISTR1="KLJ0017D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ0017D" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
Start updating the package KLJ0017D... SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
The Package Action is 1, the Update Mask is 8192 and UpdateMaskEx is 0. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
Package KLJ0017D doesn't have a source directory. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
Successfully created/updated the package KLJ0017D SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=6324 GMTDATE=Thu Jul 18 17:44:17.924 2013 ISTR0="KLJ0017D" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ0017D" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
Set share security on share \\BSMK-SCCM.klj-solutions.com\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:17 PM 6324 (0x18B4)
Created policy provider trigger for ID KLJ0017D SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
Package KLJ0017D does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
A program for package KLJ0017D has changed, therefore it needs to be replicated to all child sites. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
Package KLJ0017D is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=KLJ0017D, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
StoredPkgVersion (1) of package KLJ0017D. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
SourceVersion (1) of package KLJ0017D. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:18 PM 6324 (0x18B4)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BSMK-SCCM.klj-solutions.com SITE=KLJ PID=2364 TID=6324 GMTDATE=Thu Jul 18 17:44:19.023 2013 ISTR0="Test Motha" ISTR1="KLJ0017D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="KLJ0017D" SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:19 PM 6324 (0x18B4)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 7/18/2013 12:44:19 PM 6324 (0x18B4)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites


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

 

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.