none
Litetouch deployment failed, Return Code = -2147023504 RRS feed

  • Question

  • I suddenly started getting this error on all my task sequences. I created a new vanilla sequence and got the error on it as well. It doesn't matter if I select a x86 image task or x64. This is across multiple pieces of hardware as well. Please Help!

    <![LOG[LTI beginning deployment]LOG]!><time="11:01:31.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Event 41016 sent: LTI beginning deployment]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: "X:\Deploy\Tools\X86\TsmBootstrap.exe" /env:SAStart]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property LTIDirty is now = TRUE]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Command completed, return code = -2147023504]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147023504  0x80070570]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147023504  0x80070570]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="11:01:32.000+000" date="05-22-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Wednesday, May 22, 2013 6:06 PM

Answers

  • I found the issue with this. Apparently the computers I was running these sequences on had previous deployments run and interrupted on them. Even though the deployment wizard wasn't flagging them as "dirty" clearly there was something hanging around on the HD that was causing issues. I used diskpart to run a quick format on the OS volume and all is good. 

    Maybe this will help someone googleing in the future.

     
    • Marked as answer by Andy R S Wednesday, May 22, 2013 7:57 PM
    Wednesday, May 22, 2013 7:57 PM

All replies