none
MDT 2013 Update 2 - Failed to save environment to (80070057)_ Error during deployment RRS feed

  • Question

  • Hello,

    I am currently experiencing an issue with deploying a custom WIM using MDT 2013 Update 2. The same task and WIM successfully deployed out to this set of PCs before upgrading to Update 2.

    My WIM is Windows 7 Enterprise x64 - created virtually using VMware.  Successfully deployed and is still deploying to one set of machines - Dell laptops.  But having an issue with Fuji Siemens PCs.   Below is the error I am seeing.  This is right after the operating system has finished applying and the unattend task has ran and is about to reboot to run the sysprep but this error appears. 

    Taking a closer look at the SMSTS.log seems to have lots of errors here is a sample.

    D:\_SMSTaskSequence does not exist TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to create D:\_SMSTaskSequence (3) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003 TSManager 05/05/2016 13:55:15 1212 (0x04BC) We do not find an available volume to store the local data path TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a global environment variable _SMSTSNextInstructionPointer=54 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a TS execution environment variable _SMSTSNextInstructionPointer=54 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a global environment variable _SMSTSInstructionStackString=47 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a TS execution environment variable _SMSTSInstructionStackString=47 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Save the current environment block TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to save environment to (80070057) TSManager 05/05/2016 13:55:15 1212 (0x04BC) 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) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to persist execution state. Error 0x(80070057) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to save execution state and environment to local hard disk TSManager 05/05/2016 13:55:15 1212 (0x04BC) The task sequence execution engine can not reboot the machine because we failed to persist execution environment TSManager 05/05/2016 13:55:15 1212 (0x04BC) Fatal error is returned in check for reboot request of the action (Restart computer). Unspecified error (Error: 80004005; Source: Windows) TSManager 05/05/2016 13:55:15 1212 (0x04BC) An error (0x80004005) is encountered in execution of the task sequence TSManager 05/05/2016 13:55:15 1212 (0x04BC) Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 05/05/2016 13:55:15 1212 (0x04BC) Task Sequence Engine failed! Code: 80004005 TSManager 05/05/2016 13:55:15 1212 (0x04BC) **************************************************************************** TSManager 05/05/2016 13:55:15 1212 (0x04BC) Task sequence execution failed with error code 80004005 TSManager 05/05/2016 13:55:15 1212 (0x04BC)

    I can't post any images so am unable to show the exact error during deployment.

    Any ideas?  Am totally stuck and out of ideas.  I have tested running the TS without it injecting any drivers to see if it was a driver issue but that brings up the same issue.

    Thanks.

    Thursday, May 5, 2016 5:24 PM

All replies

  • Post a URL link to BDD.log and smsts.log.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Thursday, May 5, 2016 5:32 PM
    Moderator
  • Hi Ty,

    Thanks but I can't post links until my account is verifed, how would I do this?

    Thursday, May 5, 2016 5:39 PM
  • You can post the link it just won't be click able.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Thursday, May 5, 2016 6:52 PM
    Moderator
  • Ah ok yes here they are then.

    SMSTS.LOG

    https://onedrive.live.com/redir?resid=89109BDDACFBA476!24460&authkey=!AFLeDU-2F-1YlCg&ithint=file%2clog

    BDD.LOG

    https://onedrive.live.com/redir?resid=89109BDDACFBA476!24461&authkey=!AKXSidYYTE0ZGKw&ithint=file%2clog

    Thanks

    Thursday, May 5, 2016 6:59 PM
  • I am not really able to determine a cause from the logs. Thank you for posting them though.  Is it possible some required driver is missing in WinPE (total guess on my part).  What version of ConfigMgr are you using?

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Friday, May 6, 2016 1:18 AM
    Moderator
  • Thank you Ty.

    We are on 2012r2.  Although am not using configmgr for the deployments. 

    Would it be a driver issue if it did work before the update to update 2?

    On some further testing I think it is something to do with UEFI bios, as I've created a gen 1 and gen 2 VM and deployment fails on the gen2 but the gen 1 seems to work fine.  The deployment also works fine on Dell laptops with uefi bios switched off.

    This doesn't explain why after the update to Update 2 it might have stopped working?

    Any other pointers? I'll take a look at the drivers

    I'll try and do some more testing today.

    Thanks again.

    Friday, May 6, 2016 6:22 AM
  • Hi Ty,

    Just to give you a update after a lot testing today, I've found the PC would image if I removed the PC from AD before, I found this by naming the PC just Test.  Previously I was using the same name as I was re-imaging a PC and wanted to keep the same name.

    No idea why it's working doing this, it works using the same name on Dell laptops.

    It's very strange, am assuming this is a bug in MDT?

    We will probably be moving to W10 at some point in the near future.

    Thanks.

    Friday, May 6, 2016 6:12 PM
  • Not an MDT in my opinion. This is much more likely an issue with group policies in the OU the same computer name existed in.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Friday, May 6, 2016 6:46 PM
    Moderator
  • No group polices have changed and was able to re-image the same PCs with the same computer name and it worked fine before I upgraded to Update 2.  It could driver related I guess I haven't explorered that just yet.

    The issue is hardware dependent it seems as the same task sequence works on other hardware keeping the same computer name.

    I've found a workaround which isn't a major issue so it is not a major headache. Thanks for all the help.

    Monday, May 9, 2016 6:08 PM
  • For testing purposes, can you open a cmd prompt and create folders on the drive that you are applying the WIM too?

    If not, then you have a more general issue of not being able to write to the drive.  I have seen that with the 'Failed to save environment' errors. Doing a CLEAN of the drive or adding in the correct storage driver fixed it.

    Monday, May 9, 2016 6:23 PM