OK, I noticed I was getting driver errors when updating the DP, so I removed all drivers and added just a couple back into the image for now and put a check in the command support box. I now get a command prompt!

New errors, too! Before the task sequence window comes up, I get this:

Wpeinit.exe

This application has failed to start because wdi.sll was not found. Re-installing the application may fix this problem

That appears twice, then I get the task sequence window. I select it, then get the same error as before. Got the SMSTS.log file (errors show below). I searched around and someone suggested that my errors could be related to boundaries issues (since the DP’s it fins are remote DP’s), but I checked and my setup VLAN subnet is defined as well as the server. Any other ideas?

Filtering Content Locations.         TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

    Adding \\XXX.CSUCHICO.EDU\SMSDP\SMSPKG\XXX00001\ to Remote DP list.               TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

    Adding \\XXX.CSUCHICO.EDU\SMSPXEIMAGES$\SMSPKG\XXX00001\ to Remote DP list.          TSPxe    6/29/2009 9:34:56 AM         1976 (0x07B8)

Found 0 DPs in subnet, 0 DPs in local site, 2 DPs in remote location and 0 Multicast DPs   TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

Skipping remote content locations.         TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

!lsDPList.empty(), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2134)            TSPxe                6/29/2009 9:34:56 AM    1976 (0x07B8)

FALSE, HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635)                TSPxe    6/29/2009 9:34:56 AM         1976 (0x07B8)

Content location request for XXX00001:3 failed. (Code 0x80040102)         TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)               TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)       TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1207)         TSPxe    6/29/2009 9:34:56 AM         1976 (0x07B8)

Failed to resolve selected task sequence dependencies. Code(0x80040102)        TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

hrReturn, HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408)            TSPxe    6/29/2009 9:34:56 AM         1976 (0x07B8)

ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040102)   TSPxe    6/29/2009 9:34:56 AM    1976 (0x07B8)

ThreadToResolveAndExecuteTaskSequence returned code 0x80040102                TSPxe    6/29/2009 9:34:56 AM    1508 (0x05E4)

Setting wizard error: This task sequence cannot be run because the program files for XXX00001 cannot be located on a distribution point. For more information, please contact your system administrator or helpdesk operator.            TSPxe                6/29/2009 9:34:56 AM    1508 (0x05E4)

I had a similar issue (so did Chris Stauffer is I remember correctly)... 

The SCCM package hash hasn’t been updated yet even though the SCCM Package content is already loaded on the SCCM DP.

You need to check the SMSTS.log to determine what package your TS is failing on.

Couple of things...

First make sure ‘Command Support’ on your boot image is enabled.

Make sure you only do this action plan on the boot image that’s being used on your SCCM PXE Service Point.

Within the sccm console, proceed to your boot images, properties then the ‘Windows PE’ tab.

Verify the ‘enable command support (testing only) is checked.

Click

Click Apply.

Click ‘OK’ to the following prompt to that will re-compile WinPE and send the updated binaries to your DP.

Verify the WinPE has been updated to the SCCM PXE Service point by reviewing the Package Status messages.

Now, restart the OS Deployment sequence, within WinPE, as soon as you receive the error message click F8 to open the command prompt.

Now you can review the SMSTS.log within the X:\Windows\Temp\ directory.  This directory path may not be correct as I seem to remember also finding this log file in the root of ‘c’ in some folder that starts with a _SMS(Something)....

HTH.

-Matt

Inside the boot image properties try running the reload thingy.

Sent from my Windows Mobile® phone.

From: Murray, Mike <MMurray@csuchico.edu>
Sent: Thursday, June 25, 2009 5:28 PM
To: 'mssms@lists.myitforum.com' <mssms@lists.myitforum.com>
Subject: RE: [mssms] "this task sequence cannot be run because..."

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/

==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/