locked
Tasksequence fails in OSD on Lenovo Laptop with error code (0x80004005) RRS feed

  • Question

  • Hello everyone,

    I bought a new Lenovo T460p and have to push Win7 x64 on it via PXE OSD.

    First the Tasksequence would not even start, I figured to add the right driver packages for the T460p to the boot image.

    Now the Tasksequence will start and run trough the first steps: Atfter it sucessfully formats the disk, it wants to apply the OS Image and instantly stop with the error code (0x80004005).

    Since i could not find any more detailed information on the error i looked into the smsts.log.

    When i look trough it with CMTrace it doesnt show me any error and the last line of the log exits the formatting process with exit code 0 so it really went sucessful.

    The only lines following are:

    <![LOG[MP server http://SRV-DTP-MP01.server. Ports 80,443. CRL=false.]LOG]!><time="10:24:17.797-120" date="08-04-2016" component="TSManager" context="" type="1" thread="1468" file="utils.cpp:6075">
    <![LOG[Setting authenticator]LOG]!><time="10:24:17.828-120" date="08-04-2016" component="TSManager" context="" type="1" thread="1468" file="utils.cpp:6097">
    <![LOG[Set authenticator in transport]LOG]!><time="10:24:17.828-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="libsmsmessaging.cpp:7908">
    <![LOG[Sending StatusMessage]LOG]!><time="10:24:17.844-120" date="08-04-2016" component="TSManager" context="" type="1" thread="1468" file="libsmsmessaging.cpp:4107">
    <![LOG[Setting message signatures.]LOG]!><time="10:24:17.860-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="libsmsmessaging.cpp:1379">
    <![LOG[Setting the authenticator.]LOG]!><time="10:24:17.864-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="libsmsmessaging.cpp:1409">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SRV-DTP-MP01.server:80  CCM_POST /ccm_system/request]LOG]!><time="10:24:17.865-120" date="08-04-2016" component="TSManager" context="" type="1" thread="1468" file="libsmsmessaging.cpp:8778">
    <![LOG[Request was successful.]LOG]!><time="10:24:17.868-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="libsmsmessaging.cpp:9113">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="10:24:17.868-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="10:24:17.868-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="10:24:17.883-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:783">
    


    When I search for "fail" it shows me some other lines a little bit above:

    <![LOG[Failed to save environment to  (80070057)]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="2" thread="1468" file="environmentlib.cpp:739">
    <![LOG[TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,843)]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:843">
    <![LOG[Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="3" thread="1468" file="executionenv.cxx:843">
    <![LOG[SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,421)]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:421">
    <![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="2" thread="1468" file="executionenv.cxx:427">
    <![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="2" thread="1468" file="engine.cxx:258">
    <![LOG[Set a global environment variable _SMSTSLastActionRetryCount=0]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    <![LOG[Start executing an instruction. Instruction name: Neustart mit Windows PE ausführen. Instruction pointer: 11]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="1" thread="1468" file="engine.cxx:117">
    <![LOG[Set a global environment variable _SMSTSCurrentActionName=Neustart mit Windows PE ausführen]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=11]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    <![LOG[Set a local default variable SMSRebootMessage]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:701">
    <![LOG[Set a local default variable SMSRebootTimeout]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:701">
    <![LOG[Set a global environment variable _SMSTSLogPath=X:\WINDOWS\TEMP\SMSTSLog]LOG]!><time="10:23:53.625-120" date="08-04-2016" component="TSManager" context="" type="0" thread="1468" file="executionenv.cxx:669">
    

    I dont think thats the reason it fails but I dont have another idea...

    Also the error only occurs on the Lenovo, the Tasksequence runs perfect on every other client.
    And because I allready red it alot: Yes the Bios Clock is set to the right time on the computer.

    Anyone got a way to solve the problem?

    Regards, Paxz.

    Friday, August 5, 2016 11:01 AM

Answers

  • Does the partition that the TS selected have enough space for the image? That was the reason for our failures on another model/type device but at the same point of the TS. Check the partition that has the _SMSTaskSequence folder to see how much space it has.
    Friday, August 12, 2016 6:02 PM

All replies

  • Can you please share the complete SMSTS log file? These snippets are not really useful for troubleshooting.

    Friday, August 5, 2016 9:16 PM
  • Check the disk partition step in your task sequence, Are the drives which are created proper & is Windows applied to the correct drive.

    Thanks,

    Pranay.

    Saturday, August 6, 2016 7:19 AM
  • Check the disk partition step in your task sequence, Are the drives which are created proper & is Windows applied to the correct drive.

    Thanks,

    Pranay.

    Saturday, August 6, 2016 7:19 AM
  • Hi,

        Did the error message occur after the OS image had been downloaded completely? Check if your disk has been formatted and partitioned correctly by using the DiskPart command in WinPE, also you could examine logs: %windir%\panther\setupact.log and setuperr.log.

    Best regards,

    Jimmy 


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, August 8, 2016 10:36 AM
  • No the OS Image does not even start Downloading.

    Used Diskpart, everything formatted right. Also the Tasksequence is set to choose the next avaible formatted partition for Applying the Image.

    I cant find the path "panther" during WinPE.

    Paxz

    Friday, August 12, 2016 9:45 AM
  • Does the partition that the TS selected have enough space for the image? That was the reason for our failures on another model/type device but at the same point of the TS. Check the partition that has the _SMSTaskSequence folder to see how much space it has.
    Friday, August 12, 2016 6:02 PM
  • Hi,

       If you change to use a variable like "OSDisk" as the destination at the Apply Operating System step will it work (also remember to specify the variable value on your OS partition properties at the Format and Partition Disk step)?  

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Saturday, August 13, 2016 6:01 AM