Hi all,

I am getting the following message after my OSD has been successful. The errors don't seem to be causing any issues but I would like to confirm this and find out what the issue could be. It seems a strange error. It didn't show up for a few days but then popped up when updates were coming down and being installed. The main error message is:

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)

For further info the logs shows this:

Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs OSDSetupHook 17/07/2015 1:03:35 PM 840 (0x0348)
<![LOG[Successfully intialized Logging for TS Manager.]LOG]!><time="15:33:17.700-480" date="07-22-2015" component="TSManager" context="" type="1" thread="3348" file="tsmanager.cpp:705"> 1/01/1601 12:00:00 AM 1993560075 (0x76D3500B)
Commandline: C:\WINDOWS\CCM\TSManager.exe /service TSManager 22/07/2015 3:33:17 PM 3348 (0x0D14)
Successfully registered Task Sequencing COM Interface. TSManager 22/07/2015 3:33:18 PM 3348 (0x0D14)
Executing as a service TSManager 22/07/2015 3:33:18 PM 3348 (0x0D14)
Started ServiceMain TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Failed to restore logs from cache. Execution history may be lost. TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Task Sequence Manager executing as service main thread TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
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 22/07/2015 3:33:18 PM 2680 (0x0A78)
Task Sequence Manager could not initialize Task Sequence Environment. code 80070002 TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Task sequence execution failed with error code 80070002 TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Cleaning Up. TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Removing Authenticator TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 22/07/2015 3:33:18 PM 2680 (0x0A78)

Is that the end of the smsts.log?

I have a suspicion that your TS did not finish completely. You can look at the status messages on the site and see if there is a message that indicates the completion of the TS.

I think what is happening is that you have a update that is rebooting the machine. The result is that the TS is unable to save its state. After the reboot, the TS tried to resume but it cannot find the state file.

This is a bit more of the log below.....after that it just repeats the same thing every 1.5hrs

==========[ TsProgressUI started in process 1704 ]========== TsProgressUI 22/07/2015 3:33:19 PM 3776 (0x0EC0)
Unregistering COM classes TsProgressUI 22/07/2015 3:33:19 PM 3776 (0x0EC0)
Shutdown complete. TsProgressUI 22/07/2015 3:33:19 PM 3776 (0x0EC0)
Process completed with exit code 0 TSManager 22/07/2015 3:33:19 PM 2680 (0x0A78)
Successfully unregistered TS Progress UI. TSManager 22/07/2015 3:33:19 PM 2680 (0x0A78)
Getting active request access handle TSManager 22/07/2015 3:33:21 PM 2680 (0x0A78)
Error setting HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence\Program. code 80070002 TSManager 22/07/2015 3:33:21 PM 2680 (0x0A78)
Error - could not get package and program IDs. code 80070002 TSManager 22/07/2015 3:33:21 PM 2680 (0x0A78)
Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSManager 22/07/2015 3:33:21 PM 2680 (0x0A78)
Start to cleanup TS policy TSManager 22/07/2015 3:33:21 PM 2680 (0x0A78)
End TS policy cleanup TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
End program: TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
Error executing Task Sequence Manager service. Code 0x80070002 TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
Sending error status message TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
MP name must be set in an environment variable TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
Non fatal error 0x80004005 in sending task sequence execution status message to MP TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs TSManager 22/07/2015 3:33:23 PM 2680 (0x0A78)
<![LOG[Successfully intialized Logging for TS Manager.]LOG]!><time="16:20:14.540-480" date="07-22-2015" component="TSManager" context="" type="1" thread="1560" file="tsmanager.cpp:705"> 1/01/1601 12:00:00 AM 1993560075 (0x76D3500B)
Commandline: C:\WINDOWS\CCM\TSManager.exe /service TSManager 22/07/2015 4:20:14 PM 1560 (0x0618)
Successfully registered Task Sequencing COM Interface. TSManager 22/07/2015 4:20:14 PM 1560 (0x0618)
Executing as a service TSManager 22/07/2015 4:20:14 PM 1560 (0x0618)
Started ServiceMain TSManager 22/07/2015 4:20:14 PM 1576 (0x0628)
Failed to restore logs from cache. Execution history may be lost. TSManager 22/07/2015 4:20:14 PM 1576 (0x0628)
Task Sequence Manager executing as service main thread TSManager 22/07/2015 4:20:14 PM 1576 (0x0628)

Kerwin, Where exactly on the Server do I have to check for messages? Thanks.

It's strange how the OSD finsihed, Windows was up and running, the last sequence in the task ran correctly (it's a move computer to another OU) and then there's a 5 days gap before these messages start coming down. The only thing that happened five days after was some updates, etc installed and the computer rebooted  (We don't have update installation as part of the TS).

Hi,

>>Where exactly on the Server do I have to check for messages?

Please use the steps in the blog to check if the task sequence is complete.

Monitoring Task Sequences in ConfigMgr 2012 R2 console

Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

After creating and running I get the below message and also when I navigate away from that node and back again my new Status message query disappears:

'The status message viewer could not find the persistent query for Query ID = xxxxxx. The viewer will be invoked with a default query displaying all status messages