kev144 Posted June 25, 2014 Report post Posted June 25, 2014 hi all, been searching hi and low for this issue, driving me crazy. I am trying to capture a windows 7 image of a machine so I can then use that image to push out to other machines with the same config. When trying to capture in windows PE, it errors out with a 80070002 error. In the log file, it shows "Failed to run the action: run command line. The system cannot find the file specified. (error 80070002: source: windows)" It also says just above ZTI ERROR - unhandled error returned by ZTIbackup (0x80070002) Anyone have any ideas? I have reset the network access account to make sure its correct and can access the share I am saving the image to. I have also set the copy the content in the package to a package share on dist. points. I made sure that the allow anon connection for the smspkg$ is set aswell. These seem to have been the most common issues while searching my error. Quote Share this post Link to post Share on other sites More sharing options...
simulacra75 Posted July 1, 2014 Report post Posted July 1, 2014 I suppose the obvious question is, what is the Task Sequence actually trying to execute during the "run command line" indicated above. It must be in the actual Build & Capture Task Sequence so what command is attempting to execute? Quote Share this post Link to post Share on other sites More sharing options...
kev144 Posted July 2, 2014 Report post Posted July 2, 2014 I suppose the obvious question is, what is the Task Sequence actually trying to execute during the "run command line" indicated above. It must be in the actual Build & Capture Task Sequence so what command is attempting to execute? it is running the ZTIbackup.wsf file cscript.exe “%scriptroot\ZTIBackup.wsf” we are running a capture in PE without sysprep Quote Share this post Link to post Share on other sites More sharing options...
simulacra75 Posted July 3, 2014 Report post Posted July 3, 2014 it is running the ZTIbackup.wsf file cscript.exe “%scriptroot\ZTIBackup.wsf” we are running a capture in PE without sysprep Shouldn't it actually be cscript.exe "%scriptroot%\ZTIBackup.wsf" Quote Share this post Link to post Share on other sites More sharing options...
kev144 Posted July 3, 2014 Report post Posted July 3, 2014 Shouldn't it actually be cscript.exe "%scriptroot%\ZTIBackup.wsf" sorry yes that is what I had, I also was told to try the same line but %deployroot% It seems in the logs it gets to validating the connection to the share I want to store the image file to and the ZTI returns a error. I have the network access account set and correct. It has permissions to the share aswell. Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted July 3, 2014 Report post Posted July 3, 2014 Do you already have a captured wim file with the same name in the same directory? IIRC there is a bug that aborts the ts if that is the case. Quote Share this post Link to post Share on other sites More sharing options...
kev144 Posted July 4, 2014 Report post Posted July 4, 2014 Do you already have a captured wim file with the same name in the same directory? IIRC there is a bug that aborts the ts if that is the case. I have no wim file yet, nothing in the shared folder. Before it captures it fails with an error 80070002 at the run command line TS which is running the ZTIbackup file. Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted July 4, 2014 Report post Posted July 4, 2014 Probably a silly question, but did you run a "use toolkit package" step before calling ztibackup? Quote Share this post Link to post Share on other sites More sharing options...
kev144 Posted July 4, 2014 Report post Posted July 4, 2014 Probably a silly question, but did you run a "use toolkit package" step before calling ztibackup? I am, running toolkit, then set the backup path and then set the backup file variable. run command line (ZTIbackup) is the last step. The process has worked in the past before we upgraded to sccm 2012 R2, what ever changed during the upgrade to r2 messed something up. Quote Share this post Link to post Share on other sites More sharing options...
