KACE Product Support Question

error while running state capture utility using script

04/02/2015 1973 views
Hi All,

Running as: SYSTEM
File does not exist: C:\ProgramData\Dell\KACE\KaptureStateLauncher_v2.0.exe
Creating process returned non-zero:  C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\279\KaptureStateLauncher_v2.0.exe /i: (267) The directory name is invalid.
Error Code: 267
Status Code: 0


Debug Log

Running kbot: runkbot 279 1427966193r10
CleanupDependencies: clean up dependencies in kbot directory C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\279
CleanupDependencies: file KaptureStateLauncher_v2.0.exe is part of the dependency list, keep the file
Kbot Config Info - Start
id=279 name=Copy of KACE Kapture utility to fetch logs version=1427964371r10 type=policy
execute disconnected=false logged_off=false
execute events
Kbot Config Info - Finish
runkbot    ----- launching [path=' C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\279' program='KaptureStateLauncher_v2.0.exe' parms='/i' wait='true'] -----
(267) The directory name is invalid.
Error Code: 267
Status Code: 0

Getting above errors while running KACE KAPTURE state utility via scripts, though the path exist it says directory name is invalid.
below is my script,Kindly help to fix this issue


  1. Always Fail.

On Success


  1. Launch “ $(KACE_DEPENDENCY_DIR)\KaptureStateLauncher_v2.0.exe” with params “/i”.
  2. Upload “C:\temp\KStemp\KaptureState.zip” to the server.

On Remediation Success

On Remediation Failure

0 Comments   [ + ] Show comments


Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ