HELP!!! OSD Task Sequence Keeps Failing at Use Toolkit Package

[druiz916]

I have an urgent need to image 20 new sites at a new facility we have brought onboard. I set up the new DP and distributed all needed packages. Now when trying to image my task sequence keeps getting stuck at "use Toolkit package step. Ive checked network account settings, and Redeployed "MDT 2013 file" package which is whats under that task but still cant get it to work. Please let me know what else may need to be done on my end.

[Leon1983]

Does smsts.log highlight anything significant?

[rdevos]

Did the format and partition step run? The "Use Toolkit Package" step needs local storage to put the files on.

 

[TrialandError]

Please post your logs and we will have a better idea. We are just guessing at possible issues until then. 

[druiz916]

 

Heres an export of my SMSTS.log file.

 

Nothing ive seen that has caught my attention

 

End TS policy cleanup    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
End program:     TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
Error executing Task Sequence Manager service. Code 0x80070002    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
Sending error status message    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
MP name must be set in an environment variable    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
Non fatal error 0x80004005 in sending task sequence execution status message to MP    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
Successfully finalized logs to SMS client log directory from D:\Program Files\SMS_CCM\Logs    TSManager    10/3/2017 1:21:25 AM    13196 (0x338C)
<![LOG[Successfully intialized Logging for TS Manager.]LOG]!><time="02:23:26.636+240" date="10-03-2017" component="TSManager" context="" type="1" thread="13260" file="tsmanager.cpp:1003">         1/1/1601 12:00:00 AM    2692133200 (0xA076B150)
Commandline: "D:\Program Files\SMS_CCM\TSManager.exe" /service    TSManager    10/3/2017 2:23:26 AM    13260 (0x33CC)
Successfully registered Task Sequencing COM Interface.    TSManager    10/3/2017 2:23:26 AM    13260 (0x33CC)
Executing as a service    TSManager    10/3/2017 2:23:26 AM    13260 (0x33CC)
Started ServiceMain    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Failed to restore logs from cache. Execution history may be lost.    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Task Sequence Manager executing as service main thread    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Failed to locate the local data path. The files needed to resume the task sequence are missing.  This could be because the task sequence finished while in Windows PE.  Please check the largest available partition for SMSTSLog\smsts.log file for more information.
The system cannot find the file specified. (Error: 80070002; Source: Windows)    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Task Sequence Manager could not initialize Task Sequence Environment. code 80070002    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Task sequence execution failed with error code 80070002    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Cleaning Up.    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Removing Authenticator    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Executing command line: D:\Program.exe Files\SMS_CCM\TsProgressUI.exe /Unregister    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
CreateProcess failed. Code(0x80070002)    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Command line execution failed (80070002)    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Trying to restore client to the state it can be managed    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
CCMExec service startup type is set to enabled    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Modifying CCMExec Service to auto start.    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
Waiting for service CCMExec to exit pending state 2    TSManager    10/3/2017 2:23:26 AM    21836 (0x554C)
CCMExec Service started    TSManager    10/3/2017 2:23:27 AM    21836 (0x554C)
Waiting for CcmExec service to be fully operational    TSManager    10/3/2017 2:23:27 AM    21836 (0x554C)
CcmExec service is up and fully operational    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
Current Assigned Management Point is gsfndcescmapp11.gsf.cc with Version 8540 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ClientLocation    10/3/2017 2:23:42 AM    21836 (0x554C)
Successfully connected to MP gsfndcescmapp11.gsf.cc:80    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
Cleaning up any active TS requests in WMI.    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
No instances of CCM_TSExecutionRequest found.    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
Cleaning up any maintenance task requests in WMI.    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
No instances of SMS_MaintenanceTaskRequests found.    TSManager    10/3/2017 2:23:42 AM    21836 (0x554C)
Getting active request access handle    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Error setting HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence\Program. code 80070002    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Error - could not get package and program IDs. code 80070002    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Start to cleanup TS policy    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
End Task Sequence policy cleanup    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
End program:     TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Error executing Task Sequence Manager service. Code 0x80070002    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Sending error status message    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
MP name must be set in an environment variable    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Non fatal error 0x80004005 in sending task sequence execution status message to MP    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
Successfully finalized logs to SMS client log directory from D:\Program Files\SMS_CCM\Logs    TSManager    10/3/2017 2:23:44 AM    21836 (0x554C)
 

[druiz916]

The format and partition step did run. 

[TrialandError]

On 10/3/2017 at 2:32 PM, druiz916 said:

Failed to locate the local data path. The files needed to resume the task sequence are missing.  This could be because the task sequence finished while in Windows PE.  Please check the largest available partition for SMSTSLog\smsts.log file for more information.
The system cannot find the file specified. (Error: 80070002; Source: Windows)

Looks like its not able to save the files locally. Does the new facility have a different model computer than you usually use? I would stick a pause in the TS steps before the Toolkit step and see if there are any hidden partitions on the disk that are not being formatted.