none
MDT 2013 - Litetouch deployment failed, Return Code = -2147467259 0x80004005 RRS feed

  • Question

  • I'm attempting to deploy an image that I have recently captured with MDT.  I was able to capture the image without any problems and after capturing, it booted up properly.  But now when I go to deploy the image using a Standard Task Sequence it errors out.  It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:

    (5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.wim" 1 C: Litetouch deployment failed, Return Code = -2147467259 0x80004005 Failed to run the action: Install Operating System. Unknown error (Error: 000015F8; Source: Unknown) The execution of the group (Install) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) Failed to run the last action: Install Operating System. Execution of task sequence failed. Unknown error (Error: 000015F8; Source: Unknown) Task Sequence Engine failed! Code: enExecutionFail Task sequence execution failed with error code 80004005 Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:

    "An operating system wasn't found. Try disconnecting any drives that don't contain an operating system"

    I have tried the following to resolve this issue:

    • Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
    • Update to MDT 2013
    • Update Deployment share and completely regenerate Boot images
    • Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
    • Also tried starting deployment using USB boot disk

    I'm running out of ideas and seem to keep getting the same 8 error messages.  It's very aggravating and am hoping that someone can point me in the right direction.

    I've included some log files on Skydrive at:  https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105





    • Edited by 0324brent Tuesday, February 4, 2014 8:46 PM
    Tuesday, February 4, 2014 8:39 PM

Answers

  • I would suggest you checking the followings:

    1. Check bdd.log for what specific error returned by ImageX -> right before the error thrown "the error should explain"

    2. What is the size of the HDD?

    3. (Sorry - I didn't check the log) are you formatting the disk?

    Wednesday, April 2, 2014 6:59 AM

All replies

  • That error basically means something bad happened and I don't know what. You might want to try updating your deployment share to use the IP address and not the machine name, that can really help it you have different subnets to contend with. Also I noticed an error in your log that said "User specified local data drive E:" Do you have anything customized that tries to install to drive E? I went through the logs on recently deployed computer and did not find that string.
    Wednesday, February 5, 2014 9:43 PM
  • I also have this problem.  Any luck?
    Wednesday, March 19, 2014 4:39 PM
  • I would suggest you checking the followings:

    1. Check bdd.log for what specific error returned by ImageX -> right before the error thrown "the error should explain"

    2. What is the size of the HDD?

    3. (Sorry - I didn't check the log) are you formatting the disk?

    Wednesday, April 2, 2014 6:59 AM
  • Full BDD.log file would be helpful in this case.

    Keith Garner - keithga.wordpress.com

    Thursday, April 3, 2014 9:40 PM
    Moderator
  • I came across this post recently. I am having the same string of errors suddenly when I try to deploy any image from my MDT 2013 server now. Previous images now fail to install soon after the Inject Drivers task sequence at the Install Operating System sequence. Each time I try to deploy an image(have tried several each with different task sequences), I get the same 7 errors.

    The errors produced are:

    • Litetouch deployment failed, Return Code = -2147467259 0x80004005
    • Failed to run the action: Install Operating System.
    • Incorrect Function (Error: 00000001; Source: Windows)
    • The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    • Operation aborted (Error: 80004004; Source: Windows)
    • Failed to run the last action: Install Operating System. Execution of task sequence failed.
    • Incorrect Function (Error: 00000001; Source: Windows)
    • Task Sequence Engine failed! Code: enExecutionFail
    • Task sequence execution failed with error code 80004005
    • Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    My HD size is 146GB with about 71GB being free.

    The BDD.log file is too large to post here apparently. Here are the last bits of it.

    <![LOG[Assume this disk is the destination Disk, and verify.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[TargetPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Search for Drive: TargetPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '499577253888' and VolumeName = 'OSDisk' and VolumeSerialNumber = 'CA3BC8A9']LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Found Drive: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Property OSDisk is now = C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Target Drive Letter Found: C:]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Found OS Drive: C   0]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[New ZTIDiskPartition : \\MININT-I3DUVLI\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\MININT-I3DUVLI\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Check Disk [0] <> [0] OK to skip.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[####### NOTE:  If this is one of the  last lines in your BDD.log file, check C: for the most up to date bdd.log!!!]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">
    <![LOG[Event 41001 sent: ZTIDiskpart processing completed successfully.]LOG]!><time="11:36:58.000+000" date="09-26-2014" component="ZTIDiskpart" context="" type="1" thread="" file="ZTIDiskpart">


    • Edited by MW911 Friday, September 26, 2014 8:42 PM
    Friday, September 26, 2014 8:38 PM
  • The bdd.log file can exist in several locations, including c:\minint and x:\minint. If the last few lines of the log file are from ZTIDiskPart, then I believe you extracted the log from the x:\minint folder, but if the errors were in LTIApply, then I recommend checking the c:\minint folder instead.

    IF you want to share your bdd.log file, I recommend posting to a public site like OneDrive, and sharing the link.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, September 26, 2014 8:53 PM
    Moderator
  • Try these on the OneDrive site.

    Bdd.log from C:\minint

    https://onedrive.live.com/redir?resid=B765A32D5E17A31!109&authkey=!ACXMEsNPQowKmqw&ithint=file%2clog

    Bdd.log from X:\minint

    https://onedrive.live.com/redir?resid=B765A32D5E17A31!110&authkey=!AKUAnuMgsqxrFOo&ithint=file%2clog

    Smsts.log

    https://onedrive.live.com/redir?resid=B765A32D5E17A31!108&authkey=!ALq4xdznJS8HghQ&ithint=file%2clog

    Friday, September 26, 2014 11:07 PM
  • Sorry, no, these aren't the correct files.

    Try c:\windows\temp\deploymentlogs

    or  x:\windows\temp\deploymentlogs


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, September 26, 2014 11:26 PM
    Moderator
  • Here's the BDD.Log file from the C:\Windows\Temp\Deploymentlogs folder.

    https://onedrive.live.com/redir?resid=B765A32D5E17A31!111&authkey=!ACmiRygauRK6Up4&ithint=file%2ctxt

    Tuesday, September 30, 2014 6:15 PM
  • Weird I do not see the same errors you list above...

    This is a halt in the task sequencer... Somewhere...

    We will need the following file: SMSTS.LOG (it may be in X:\WINDOWS\TEMP\SMSTSLog, but check all versions )

    The smsts.log file should contain the reason why it failed near ZTINextPhase.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, September 30, 2014 8:17 PM
    Moderator
  • Here is the SMSTS.log file from X:\WINDOWS\TEMP\

    https://onedrive.live.com/redir?resid=B765A32D5E17A31!112&authkey=!AM7WdtjkIEcutPY&ithint=file%2clog

    Tuesday, September 30, 2014 8:24 PM
  • Wow, that's messed up. :^(

    Was this deployment share at any point upgraded from a previous version of MDT?

    If so I think you may have some corrupted files. LTIApply.wsf shouldn't just crash like that.

    If I were at the machine I would try running the command manually from the WinPE Command prompt just *after* the crash. :

    cscript LTIApply.wsf /debug:true /debugcapture

    to see what happens.

    Otherwise, I try creating a new Deployment share that is not from a pre-existing source to see if you can reproduce the issue.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, September 30, 2014 8:34 PM
    Moderator
  • I'll try the command. I still have the target computer at the F8 "DOS" screen. BTW, looks like you may be in the Pacific NW. I'm up in Mountlake Terrace.
    Tuesday, September 30, 2014 8:36 PM
  • Where is LTIApply.wsf located?
    Tuesday, September 30, 2014 8:41 PM
  • You may need to connect to your Deployment Share:

    net use * \\server\deploymentshare$ /u:Domain\UserName *

    z:

    cscript z:\scripts\ltiapply.wsf /debug:true /debugcapture


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, September 30, 2014 8:44 PM
    Moderator
  • Ok, DUH, same place as when you run a capture sequence from a mapped drive on the deployment server.

    Could a Windows update on the server have done any of this? All my deployments were going great until recently. 

    Tuesday, September 30, 2014 8:50 PM
  • I got it to finally work. I ended up creating a new deployment share and copying, at first, just one of the .WIM images to it along with its task sequence and trying it. Eventually, I copied over everything else and so far so good. 
    Thursday, October 2, 2014 2:12 PM
  • Hi,

    To whom who have this issue when deploy to Hyper-V VM , Give the VM more then 1GB RAM- that's resolved this error on my situation.

    • Proposed as answer by Antoine M76 Sunday, January 21, 2018 8:23 PM
    Monday, May 18, 2015 5:08 AM
  • For me, I removed the 'install operating system' step in the TS and re-added it as I had updated the image when it stopped working. I also reprovisioned the VM drive with more space which may also have helped. Both are small easy steps and worth a try. :)
    Monday, August 10, 2015 7:28 AM
  • We got the same error and the reason was a Windows Update. (via Packages)

    Do you work with Windows Patches via Packages?

    Try cleaning them up and rebuild your deployment share and try again. Currently we are looking which patch it is. (Windows 7 ENT x64)


    Ventrex

    Monday, August 10, 2015 10:08 AM
  • Hi,

    To whom who have this issue when deploy to Hyper-V VM , Give the VM more then 1GB RAM- that's resolved this error on my situation.

    Works for me, thank you.
    Sunday, January 21, 2018 8:24 PM
  • i am checked but RAM and is HDD more then 80 GB is 
    Monday, February 26, 2018 4:53 AM