/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Kace K1000 Kapture State kscript is failing on most machines, but logs say it succeeded

12/14/2017 1227 views
I'm getting a ton of log upload failures in my patch schedules, so I'm trying to run Kapture State to gather logs to determine why this is happening. However, the kscript is failing on 2/3 of the machines I run it on. The kscript run schedule reports that it's failed, and there are no uploaded files on the device summary page.

I looked at the logs of Kapture State running, however, and it says it ran perfectly! What is going on? Here's what I see when looking at the kscript log:

Output Log
Running as SYSTEM
Creating process returned non-zero: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\109\KaptureState_v2.0.exe /s: (0) The operation completed successfully.
Error Code: 0
Status Code: 1

Activity Log

verify - on_verify_success
verify - on_verify_failure
verify - launch_program
Launching program: 'C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\109\KaptureState_v2.0.exe' '/s' wait='true'

Debug Log


Running kbot: runkbot 109 1513262157 KBotScript::LogScriptInfo - Start id=109 name=KaptureState version=1513262157 type=policy execute disconnected=false logged_off=false execute events KBotScript::LogScriptInfo - Finish KBotScript::LogScriptInfo - Start id=109 name=KaptureState version=1513262157 type=policy execute disconnected=false logged_off=false execute events KBotScript::LogScriptInfo - Finish KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Quest\KACE\kbots_cache\\packages\kbots\109\ CleanupDependencies: file KaptureState_v2.0.exe is part of the dependency list, keep the file runkbot ----- launching [path='C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\109' program='KaptureState_v2.0.exe' parms='/s' wait='true'] -----


0 Comments   [ + ] Show comments

Comments


All Answers

0
From the script I can tell you are trying to run Kapture State v2.0, if your devices are running Agent 8.0 then you need to run v3.0 which you can find here: https://support.quest.com/kb/234337
Answered 12/18/2017 by: Josh_H
Senior White Belt

Don't be a Stranger!

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

Sign up! or login

Share

 
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