none
Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Question

  • running Windows Server 2008 R2
    Roles:
    DHCP server
    File Services
    Network Policy and Access Services
    WDS
    all the above are an existing configuration and still have some Windows XP images setup on WDS. 

    installed MDT 2010 to create and deploy windows 7 images.

    when i attempt to capture a Windows 7 image from an existing install (with the programs and settings already present), i get almost all the way through until it comes to the task of running sysprep, then it fails. 
    2 errors are present when viewing details:
    FAILURE (6111): 255:Run Sysprep.exe.
    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    i have reviewed the LiteTouch, BDD, and smsts log files.

    excerpt from Litetouch related to the failure:

    <![LOG[About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAContinue]LOG]!><time="13:01:23.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="13:11:33.000+000" date="02-16-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: MSHTA.exe "C:\MININT\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    and that's the end of the log file. 

    excerpt from BDD related to the failure:

    <![LOG[About to run command: C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /quit]LOG]!><time="13:01:32.000+000" date="02-16-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[ZTI Heartbeat: command has been running for 6 minutes (process ID 2216)]LOG]!><time="13:07:00.000+000" date="02-16-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[Return code from command = 255]LOG]!><time="13:11:33.000+000" date="02-16-2010" component="LTISysprep" context="" type="1" thread="" file="LTISysprep">
    <![LOG[FAILURE ( 6111 ): 255: Run Sysprep.exe.]LOG]!><time="13:11:33.000+000" date="02-16-2010" component="LTISysprep" context="" type="3" thread="" file="LTISysprep">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="13:11:33.000+000" date="02-16-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="13:11:34.000+000" date="02-16-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    there's still more after that in the log, but doesn't look like it's related.

    excerpt from smsts related to the failure:

    <![LOG[Failed to run the action: Execute Sysprep. 
    Unknown error (Error: 000017DF; Source: Unknown)]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=6111]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="13:11:33.639+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Capture Image) decides whether to continue execution]LOG]!><time="13:11:33.670+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="instruction.cxx:3210">
    <![LOG[Let the parent group (State Restore) decide whether to continue execution]LOG]!><time="13:11:33.670+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="instruction.cxx:2461">
    <![LOG[The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Execute Sysprep. Execution of task sequence failed.
    Unknown error (Error: 000017DF; Source: Unknown)]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utility.cxx:302">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762)]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="tsmanager.cpp:762">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="tsmanager.cpp:762">
    <![LOG[****************************************************************************]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tsmanager.cpp:784">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="tsmanager.cpp:785">
    <![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="13:11:33.702+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tsmanager.cpp:578">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="13:11:33.733+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utils.cpp:1404">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513)]LOG]!><time="13:11:33.889+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="resolvesource.cpp:513">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="13:11:33.889+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="environmentlib.cpp:855">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="13:11:33.889+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="commandline.cpp:229">
    <![LOG[Set command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="13:11:33.889+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="commandline.cpp:707">
    <![LOG[Executing command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="13:11:33.889+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="commandline.cpp:805">
    <![LOG[==========[ TsProgressUI started in process 872 ]==========]LOG]!><time="13:11:33.904+360" date="02-16-2010" component="TsProgressUI" context="" type="1" thread="296" file="winmain.cpp:327">
    <![LOG[Command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="13:11:33.904+360" date="02-16-2010" component="TsProgressUI" context="" type="0" thread="296" file="winmain.cpp:330">
    <![LOG[Unregistering COM classes]LOG]!><time="13:11:33.904+360" date="02-16-2010" component="TsProgressUI" context="" type="1" thread="296" file="winmain.cpp:202">
    <![LOG[Unregistering class objects]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TsProgressUI" context="" type="1" thread="296" file="winmain.cpp:503">
    <![LOG[Shutdown complete.]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TsProgressUI" context="" type="1" thread="296" file="winmain.cpp:520">
    <![LOG[Process completed with exit code 0]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="commandline.cpp:1102">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="utils.cpp:1963">
    <![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654)]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="0" thread="3628" file="tsmanager.cpp:654">
    <![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="3" thread="3628" file="tsmanager.cpp:684">
    <![LOG[Sending error status message]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tsmanager.cpp:685">
    <![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tsmanager.cpp:1536">
    <![LOG[Finalizing logging from process 3624]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tslogging.cpp:1736">
    <![LOG[LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\".]LOG]!><time="13:11:33.920+360" date="02-16-2010" component="TSManager" context="" type="1" thread="3628" file="tslogging.cpp:1803">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="13:11:33.936+360" date="02-16-2010" component="TSMBootstrap" context="" type="1" thread="3588" file="commandline.cpp:1102">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="13:11:33.936+360" date="02-16-2010" component="TSMBootstrap" context="" type="1" thread="3588" file="tsmbootstrap.cpp:1117">

    wasn't sure where to stop on that one. 

    after spending the last 3 or so hours sifting through google, technet, and other various search results, i haven't come up with information specific to my situation. i have found quite afew threads about the return code i put in the subject line, but no real resolution. does anyone have any ideas what i'm missing? Johan? are you out there? :)
    Wednesday, February 17, 2010 4:05 AM

Answers

  • Okay, Japrice...try this:

    On your Windows 7 reference PC, open the registry editor.  Navigate to HKLM\system\setup.  Look for a multi-string value called "CloneTag".  I'm guessing it's not there.

    Add a new multi-string value, name it "CloneTag".  The actual value is not important.  I'm not sure if case on the name is important, so I mimicked what the error suggested.

    Export the HKLM\system\setup key and save to a .reg file.

    Edit the .reg file, and remove all other entries except for the CloneTag value.

    Run the cscript to launch the Task Sequence selector.  Select your Sysprep and Capture Task Sequence.  Enter your credentials, and go.

    When it gets to the part where it is executing sysprep, run your .reg file to quickly import the CloneTag multi-string value.  If you see it proceed to PE, then you should be in the clear.

    I JUST this moment got this to work.  :)  :)  :)  I, too, have been researching this all week long.  Good luck!
    • Proposed as answer by Chris Kuebler Friday, February 19, 2010 8:51 PM
    • Marked as answer by japrice Monday, February 22, 2010 8:59 PM
    Friday, February 19, 2010 8:51 PM

All replies

  • I think that you and I are having the same, or a similar problem.  I also am unable to capture a Windows 7 custom image using a "Sysprep and Capture" Task Sequence.  I'm patiently awaiting a response here:

    http://social.technet.microsoft.com/Forums/en/mdt/thread/553bec59-d795-4b89-8328-19a38161eff3

    I've seen solutions that suggest disabling the BuildMassStorageSection in sysprep.inf, but I'm still not real clear on how to go about doing that since the MDT 2010 Task Sequence is driving Sysprep.
    Wednesday, February 17, 2010 2:22 PM
  • I think that you and I are having the same, or a similar problem.  I also am unable to capture a Windows 7 custom image using a "Sysprep and Capture" Task Sequence.  I'm patiently awaiting a response here:

    http://social.technet.microsoft.com/Forums/en/mdt/thread/553bec59-d795-4b89-8328-19a38161eff3

    I've seen solutions that suggest disabling the BuildMassStorageSection in sysprep.inf, but I'm still not real clear on how to go about doing that since the MDT 2010 Task Sequence is driving Sysprep.
    i agree. if not the same, very similar issues. hopefully, one of us will find a solution. if i'm first, i'll let you know what i did to remedy my issue.
    Wednesday, February 17, 2010 3:07 PM
  • To disable the BuildMassStorageSection in sysprep.inf, disable the "Add Mass Storage Drivers to sysprep.inf for XP and 2003" from the task sequence.

    Additionally, you may want to go to your OS info tab and edit the Sysprep.inf, as such:

    [Sysprep]
    BuildMassStorageSection=NO

    Mind you, I'm not sure exactly what happens in the "background", but I assume disabling the "Add Mass Storage" means sysprep doesn't throw a BMSD switch.
    Wednesday, February 17, 2010 3:34 PM
  • Wow...never considered scrutinizing the properties of the Task Sequence!  I had been going step by step literally, without stopping to look around.  Gotta remember to do that more...

    You make a good suggestion.  However, I just tried disabling this step in the "Sysprep and Capture" Task Sequence and I still get the same result.  :(  I even marked the checkbox to continue on error.  (I remembered to Update Deployment Share after making adjustments to the Task Sequence.)

    I've had the "BuildMassStorageSection=NO" in [Sysprep] for the local reference computer's sysprep.inf for some time now.  But that, also, doesn't seem to help.

    Wednesday, February 17, 2010 5:12 PM
  • well, thinking it was a configuration issue that i may have mussed up, i deleted the deployment share and everything associated with it, then started over. i booted to my pe iso disc and was able to get the OS installed, but when it attempted to continue with capturing an image, i received the same error again. this time i noticed it's at the point where it's "processing generalize phase sysprep plugins..." as the window comes up behind the popup informing me that sysprep stopped responding and had to shut down. once i close out of that prompt, i get the Deployment Summary with the error info. my thought is, it has to be something in the xml associated with the task sequence, but i don't know where to look to figure out where the configuration is incorrect. any more ideas?

    Thursday, February 18, 2010 12:55 AM
  • Hrm.  Good idea scraping the deployment share and starting from square one.  Though, that stinks that it didn't work out.

    This seems like a Herculean stop for the use of MDT 2010 to deploy Windows 7.  Are there any other avenues to explore to find support for this product?
    Thursday, February 18, 2010 2:09 PM
  • *update*
    good news, sorta. i was able to get a base image of windows to install, but errored again on sysprep. i tried a different approach to syprep and capture the image and that was to get to the litetouch.vbs script on the imaging server from the client computer via Explorer. while i was able to get to the script and get it to launch, when it came to the credentials part, i received the error "invalid credentials: network path not found (80070035)". and... i can't find any solid information online about that. i've tried both the local admin creds and the domain acct i'm using for deploying, neither are able to get me past that screen. any suggestions?
    Thursday, February 18, 2010 2:43 PM
  • *update*
    good news, sorta. i was able to get a base image of windows to install, but errored again on sysprep. i tried a different approach to syprep and capture the image and that was to get to the litetouch.vbs script on the imaging server from the client computer via Explorer. while i was able to get to the script and get it to launch, when it came to the credentials part, i received the error "invalid credentials: network path not found (80070035)". and... i can't find any solid information online about that. i've tried both the local admin creds and the domain acct i'm using for deploying, neither are able to get me past that screen. any suggestions?

    Awesome!  And I may have your answer:

    http://blogs.technet.com/msdeployment/archive/2009/09/18/fix-for-multiple-connections-to-a-server-or-shared-resource-by-the-same-user-using-more-than-one-user-name-are-not-allowed-problem-with-mdt-2010.aspx

    This stems from the inability to use two different sets of credentials to map a drive or a UNC path.  On this blog page, there is a script correction that will fix the mapping/UNC path credential problem.

    If this fixes it for you where you are able to take an image, you're going to need to explain a little further what it is you did with litetouch.vbs...
    • Proposed as answer by surfer10 Monday, November 28, 2011 3:00 PM
    Thursday, February 18, 2010 2:55 PM
  • ok, i tried that fix, but it didn't seem to change anything. what i did try was using the private ip address for the image server (two nics, public/dns side and private/dhcp side) to get to the litetouch script. i ran the script, used the private ip address as the path to the MDT test share, and entered my domain creds. this time it made it past and launched sysprep, but i received a different error now.
    FAILURE (Err): -2147024894 0x80070002: Test for CloneTag in registry to verify Sysprep completed. - Unable to open registry key "HKLM\System\Seteup\CloneTag" for reading.

    BDD log (from the MININT folder)

    <![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:32:14.000+000" date="02-18-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259  0x80004005]LOG]!><time="10:32:14.000+000" date="02-18-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

    LiteTouch log (again from the MININT folder)

    <![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="10:32:14.000+000" date="02-18-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259  0x80004005]LOG]!><time="10:32:14.000+000" date="02-18-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

    last section of the smsts log

    <![LOG[Start executing the command line: cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"]LOG]!><time="10:20:03.326+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="instruction.cxx:2928">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:20:03.326+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="instruction.cxx:2957">
    <![LOG[Expand a string: ]LOG]!><time="10:20:03.326+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="executionenv.cxx:782">
    <![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTISysprep.wsf"]LOG]!><time="10:20:03.326+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 6191]LOG]!><time="10:20:07.756+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="commandline.cpp:1102">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:20:07.756+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="instruction.cxx:3010">
    <![LOG[Failed to run the action: Execute Sysprep. 
    Unknown error (Error: 0000182F; Source: Unknown)]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="instruction.cxx:3101">
    <![LOG[Sending status message . . .]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utility.cxx:302">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=6191]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="10:20:07.803+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Capture Image) decides whether to continue execution]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="instruction.cxx:3210">
    <![LOG[Let the parent group (State Restore) decide whether to continue execution]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="instruction.cxx:2461">
    <![LOG[The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="instruction.cxx:2424">
    <![LOG[Failed to run the last action: Execute Sysprep. Execution of task sequence failed.
    Unknown error (Error: 0000182F; Source: Unknown)]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="engine.cxx:214">
    <![LOG[Sending status message . . .]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utility.cxx:292">
    <![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="10:20:07.834+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utility.cxx:302">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762)]LOG]!><time="10:20:07.850+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="tsmanager.cpp:762">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="10:20:07.850+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="tsmanager.cpp:762">
    <![LOG[****************************************************************************]LOG]!><time="10:20:07.850+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tsmanager.cpp:784">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="10:20:07.850+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="tsmanager.cpp:785">
    <![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="10:20:07.850+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tsmanager.cpp:578">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="10:20:07.865+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utils.cpp:1404">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513)]LOG]!><time="10:20:07.897+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="resolvesource.cpp:513">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="10:20:07.912+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="environmentlib.cpp:855">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="10:20:07.912+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="commandline.cpp:229">
    <![LOG[Set command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="10:20:07.912+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="commandline.cpp:707">
    <![LOG[Executing command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="10:20:07.912+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="commandline.cpp:805">
    <![LOG[==========[ TsProgressUI started in process 2372 ]==========]LOG]!><time="10:20:07.943+360" date="02-18-2010" component="TsProgressUI" context="" type="1" thread="2368" file="winmain.cpp:327">
    <![LOG[Command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="10:20:07.943+360" date="02-18-2010" component="TsProgressUI" context="" type="0" thread="2368" file="winmain.cpp:330">
    <![LOG[Unregistering COM classes]LOG]!><time="10:20:07.943+360" date="02-18-2010" component="TsProgressUI" context="" type="1" thread="2368" file="winmain.cpp:202">
    <![LOG[Unregistering class objects]LOG]!><time="10:20:07.943+360" date="02-18-2010" component="TsProgressUI" context="" type="1" thread="2368" file="winmain.cpp:503">
    <![LOG[Shutdown complete.]LOG]!><time="10:20:07.943+360" date="02-18-2010" component="TsProgressUI" context="" type="1" thread="2368" file="winmain.cpp:520">
    <![LOG[Process completed with exit code 0]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="commandline.cpp:1102">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="utils.cpp:1963">
    <![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654)]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="0" thread="2284" file="tsmanager.cpp:654">
    <![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="3" thread="2284" file="tsmanager.cpp:684">
    <![LOG[Sending error status message]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tsmanager.cpp:685">
    <![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tsmanager.cpp:1536">
    <![LOG[Finalizing logging from process 2288]LOG]!><time="10:20:07.959+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tslogging.cpp:1736">
    <![LOG[LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\".]LOG]!><time="10:20:08.053+360" date="02-18-2010" component="TSManager" context="" type="1" thread="2284" file="tslogging.cpp:1803">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="10:20:08.068+360" date="02-18-2010" component="TSMBootstrap" context="" type="1" thread="712" file="commandline.cpp:1102">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="10:20:08.068+360" date="02-18-2010" component="TSMBootstrap" context="" type="1" thread="712" file="tsmbootstrap.cpp:1117">


    Thursday, February 18, 2010 7:06 PM
  • Look in the log file in c:\windows\system32\sysprep\panther.  That will cover what is causing sysprep to fail.
    Tim Mintner Principal Consultant Xtreme Consulting Group http://deployment.xtremeconsulting.com
    • Proposed as answer by Makaveli1976 Sunday, May 26, 2013 3:12 PM
    Thursday, February 18, 2010 10:06 PM
    Moderator
  • thanks for the suggestion Tim! i looked at the setuperr.log and with it i found out there's an issue with the audio controller driver for GX620's. i scrapped working on using a GX620 and opted to try capturing an image for an Optiplex 780. i thought it was going to be smooth sailing because sysprep actually ran, but when it got to the point to restart and capture, the computer just sat there. BDD.exe was still running, but nothing else happened. 

    i checked the BDD.log file and here's the last snippet:

    ------  Applying bootable Windows PE image ------ LTIApply 2/19/2010 1:25:23 PM 0 (0x0000)
    LTI applying Windows PE LTIApply 2/19/2010 1:25:23 PM 0 (0x0000)
    Will boot into Windows PE architecture x86 to match OS being deployed. LTIApply 2/19/2010 1:25:23 PM 0 (0x0000)
    Copying \\CLLADHCPWDS\MDT\Boot\LiteTouchPE_x86.wim to C:\sources\boot.wim LTIApply 2/19/2010 1:25:23 PM 0 (0x0000)
    ZTI ERROR - Unhandled error returned by LTIApply: Path not found (76) LTIApply 2/19/2010 1:25:49 PM 0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    Property RetVal is now = -2147467259 LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    CleanStartItems Complete LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    About to run command: MSHTA.exe "\\clladhcpwds\MDT\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)

    checking the LiteTouch.log file, here's the last section:

    LTI beginning deployment LiteTouch 2/19/2010 1:24:19 PM 0 (0x0000)
    About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAStart LiteTouch 2/19/2010 1:24:19 PM 0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    Property RetVal is now = -2147467259 LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    CleanStartItems Complete LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)
    About to run command: MSHTA.exe "\\clladhcpwds\MDT\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml LiteTouch 2/19/2010 1:25:49 PM 0 (0x0000)

    checking the smsts.log file, here's the last portion:

    Expand a string: TSManager 2/19/2010 1:25:23 PM 2560 (0x0A00)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /PE TSManager 2/19/2010 1:25:23 PM 2560 (0x0A00)
    Process completed with exit code 76 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    !--------------------------------------------------------------------------------------------! TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Failed to run the action: Apply Windows PE. 
    Unknown error (Error: 0000004C; Source: Unknown) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Sending status message . . . TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Set a global environment variable _SMSTSLastActionRetCode=76 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Clear local default environment TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Let the parent group (Capture Image) decides whether to continue execution TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Let the parent group (State Restore) decide whether to continue execution TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Failed to run the last action: Apply Windows PE. Execution of task sequence failed.
    Unknown error (Error: 0000004C; Source: Unknown) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Sending status message . . . TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,762) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    **************************************************************************** TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Task sequence execution failed with error code 80004005 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Cleaning Up. Removing Authenticator TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Cleaning up task sequence folder TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,513) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Command line for extension .exe is "%1" %* TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Set command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Executing command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    ==========[ TsProgressUI started in process 364 ]========== TsProgressUI 2/19/2010 1:25:49 PM 2844 (0x0B1C)
    Command line: "C:\MININT\Tools\X86\TsProgressUI.exe" /Unregister TsProgressUI 2/19/2010 1:25:49 PM 2844 (0x0B1C)
    Unregistering COM classes TsProgressUI 2/19/2010 1:25:49 PM 2844 (0x0B1C)
    Unregistering class objects TsProgressUI 2/19/2010 1:25:49 PM 2844 (0x0B1C)
    Shutdown complete. TsProgressUI 2/19/2010 1:25:49 PM 2844 (0x0B1C)
    Process completed with exit code 0 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Successfully unregistered TS Progress UI. TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,654) TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Sending error status message TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Finalizing logging from process 2164 TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\". TSManager 2/19/2010 1:25:49 PM 2560 (0x0A00)
    Process completed with exit code 2147500037 TSMBootstrap 2/19/2010 1:25:49 PM 3600 (0x0E10)
    Exiting with return code 0x80004005 TSMBootstrap 2/19/2010 1:25:49 PM 3600 (0x0E10)


    i'm researching this issue now, but if anyone has encountered this and can shed some light, i'd appreciate it. i've been working on this for the past week and have moved forward maybe two steps.
    Friday, February 19, 2010 8:15 PM
  • Okay, Japrice...try this:

    On your Windows 7 reference PC, open the registry editor.  Navigate to HKLM\system\setup.  Look for a multi-string value called "CloneTag".  I'm guessing it's not there.

    Add a new multi-string value, name it "CloneTag".  The actual value is not important.  I'm not sure if case on the name is important, so I mimicked what the error suggested.

    Export the HKLM\system\setup key and save to a .reg file.

    Edit the .reg file, and remove all other entries except for the CloneTag value.

    Run the cscript to launch the Task Sequence selector.  Select your Sysprep and Capture Task Sequence.  Enter your credentials, and go.

    When it gets to the part where it is executing sysprep, run your .reg file to quickly import the CloneTag multi-string value.  If you see it proceed to PE, then you should be in the clear.

    I JUST this moment got this to work.  :)  :)  :)  I, too, have been researching this all week long.  Good luck!
    • Proposed as answer by Chris Kuebler Friday, February 19, 2010 8:51 PM
    • Marked as answer by japrice Monday, February 22, 2010 8:59 PM
    Friday, February 19, 2010 8:51 PM
  • Okay, Japrice...try this:

    On your Windows 7 reference PC, open the registry editor.  Navigate to HKLM\system\setup.  Look for a multi-string value called "CloneTag".  I'm guessing it's not there.

    Add a new multi-string value, name it "CloneTag".  The actual value is not important.  I'm not sure if case on the name is important, so I mimicked what the error suggested.

    Export the HKLM\system\setup key and save to a .reg file.

    Edit the .reg file, and remove all other entries except for the CloneTag value.

    Run the cscript to launch the Task Sequence selector.  Select your Sysprep and Capture Task Sequence.  Enter your credentials, and go.

    When it gets to the part where it is executing sysprep, run your .reg file to quickly import the CloneTag multi-string value.  If you see it proceed to PE, then you should be in the clear.

    I JUST this moment got this to work.  :)  :)  :)  I, too, have been researching this all week long.  Good luck!
    well, this is interesting. i checked HKLM>SYSTEM>Setup and there's already a CloneTag key. the Value data is Mon Jul 13 21:55:53 2009
    Friday, February 19, 2010 9:40 PM
  • Export it, and see if importing it DURING the "executing sysprep" part of the Task Sequence gets you past where it bombs.  Something to do with the Task Sequence deletes it prematurely for some reason...

    Friday, February 19, 2010 10:20 PM
  • Export it, and see if importing it DURING the "executing sysprep" part of the Task Sequence gets you past where it bombs.  Something to do with the Task Sequence deletes it prematurely for some reason...

    ok, i imported the registry key afew times while i was working on this capture and successfully got it to restart and continue the capture. now i can go back and really customize it and re-capture it! 

    thanks Chris, Tim, and FNO for the help! 
    Monday, February 22, 2010 8:35 PM