/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


Help understanding agent log for failed agent upgrade

04/29/2020 125 views

Hey all,

I have a device that has not successfully upgraded the agent to version 10.0.113. I was wondering if someone might be able to look at this log and tell me why it didn't successfully upgrade? Thanks!


Latest Log for 5.2+ Windows Agent Upgrade on PC9240 Show All ]

Started:04/29/2020 10:01:05
Finished:04/29/2020 10:03:12
Elapsed Time:127 seconds
Status:1

Output Log

Running as SYSTEM
Launched Process: cmd.exe
1 file(s) copied.
Launched Process: cmd.exe
Launched Process: msiexec.exe

Activity Log

verify - launch_program
Launching program: 'C:\windows\System32\cmd.exe' '/c if not exist "C:\ProgramData\Quest\KACE\user" mkdir "C:\ProgramData\Quest\KACE\user"' wait='true'
verify - launch_program
Launching program: 'C:\windows\System32\cmd.exe' '/c copy "C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\5\ampagent-10.0.113-x86.msi" "C:\ProgramData\Quest\KACE\user\ampagent-10.0.113-x86.msi"' wait='true'
verify - on_verify_success
verify - on_verify_failure
verify - launch_program
Launching program: 'C:\windows\System32\msiexec.exe' '/qn /norestart /l*v "C:\ProgramData\Quest\KACE\user\ampmsi.log" /i "C:\ProgramData\Quest\KACE\user\ampagent-10.0.113-x86.msi" HOST=kace.grinnell.edu' wait='false'

Debug Log

Running kbot: runkbot 5 1587744209
KBotScript::LogScriptInfo - Start
id=5 name=5.2+ Windows Agent Upgrade version=1587744209 type=system
execute disconnected=false logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScript::LogScriptInfo - Start
id=5 name=5.2+ Windows Agent Upgrade version=1587744209 type=system
execute disconnected=false logged_off=true
execute events
KBotScript::LogScriptInfo - Finish
KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Quest\KACE\kbots_cache\\packages\kbots\5\
CleanupDependencies: file ampagent-10.0.113-x86.msi is part of the dependency list, keep the file
runkbot    ----- launching [path='C:\windows\System32' program='cmd.exe' parms='/c if not exist "C:\ProgramData\Quest\KACE\user" mkdir "C:\ProgramData\Quest\KACE\user"' wait='true'] -----
runkbot    ----- completed [exitCode=0] -----
runkbot    ----- launching [path='C:\windows\System32' program='cmd.exe' parms='/c copy "C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\5\ampagent-10.0.113-x86.msi" "C:\ProgramData\Quest\KACE\user\ampagent-10.0.113-x86.msi"' wait='true'] -----
runkbot    ----- completed [exitCode=0] -----
runkbot    ----- launching [path='C:\windows\System32' program='msiexec.exe' parms='/qn /norestart /l*v "C:\ProgramData\Quest\KACE\user\ampmsi.log" /i "C:\ProgramData\Quest\KACE\user\ampagent-10.0.113-x86.msi" HOST=kace.grinnell.edu' wait='false'] -----
runkbot    ----- completed [exitCode=0] -----
0 Comments   [ + ] Show comments

Comments


All Answers

0

The log is reporting a successful install.  Do you still have the following file?

C:\ProgramData\Quest\KACE\user\ampmsi.log


It is just that the device is not checking into the appliance?

Answered 05/01/2020 by: KevinG
4th Degree Black Belt

  • Yep, it just needed to check in. Thanks!

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