none
This could be because the task sequence finished while in Windows PE RRS feed

  • Question

  •  

    does anyone have any idea ?

     

    Started ServiceMain TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Failed to restore logs from cache. Execution history may be lost. TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Task Sequence Manager executing as service main thread TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    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.
    Unknown error (Error: 80070002; Source:
    Unknown) TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Task Sequence Manager could not initialize Task Sequence Environment. code 80070002
     TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Task sequence execution failed with error code 80070002 TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Cleaning Up. Removing Authenticator TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 04.08.2008 11:07:52 1256 (0x04E8)
    Executing command line: "C:\WINNT\system32\CCM\TsProgressUI.exe" /Unregister TSManager 04.08.2008 11:07:52 1256 (0x04E8)


    ==========[ TsProgressUI started in process 1304 ]========== TsProgressUI 04.08.2008 11:07:53 1300 (0x0514)
    Unregistering COM classes TsProgressUI 04.08.2008 11:07:53 1300 (0x0514)
    Shutdown complete. TsProgressUI 04.08.2008 11:07:53 1300 (0x0514)
    Process completed with exit code 0 TSManager 04.08.2008 11:07:53 1256 (0x04E8)
    Successfully unregistered TS Progress UI. TSManager 04.08.2008 11:07:53 1256 (0x04E8)
    Getting active request access handle TSManager 04.08.2008 11:07:53 1256 (0x04E8)
    Package ID: 00500060, Program ID: * TSManager 04.08.2008 11:07:53 1256 (0x04E8)
    Policy cleanup done TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    Error executing Task Sequence Manager service. Code 0x80070002 TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    Sending error status message TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    MP name must be set in an environment variable TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    Non fatal error sending status message. Code 0x80004005 TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    Resuming SMS Components TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    Waiting for CcmExec service to be fully operational TSManager 04.08.2008 11:07:54 1256 (0x04E8)
    CcmExec service is up and fully operational TSManager 04.08.2008 11:08:44 1256 (0x04E8)

    Monday, August 4, 2008 7:34 AM

Answers

  • Can you offer more insight as to what you were doing?  Perhaps adding something as simple as a "Wait" step to ensure you've completed the step before attempting to continue/reboot into the new OS?  Hard to say without more information.

     

    Nathan Barnett

     

    This posting is provided “AS IS” with no warranties and confers no rights.

     

    Thursday, August 7, 2008 8:59 PM

All replies

  • Can you offer more insight as to what you were doing?  Perhaps adding something as simple as a "Wait" step to ensure you've completed the step before attempting to continue/reboot into the new OS?  Hard to say without more information.

     

    Nathan Barnett

     

    This posting is provided “AS IS” with no warranties and confers no rights.

     

    Thursday, August 7, 2008 8:59 PM
  • Check your local drive for SMSTS.log and see if any other errors are shown in there.

    It seems to me that one of the tasks sequences is exiting the process during the WinPE environment and the task sequence is exiting.

     

    Make sure you are not formatting or cleaning up the local drive at all during the deployment process that might be wiping out the local files.
    Monday, August 11, 2008 3:58 AM