/build/static/layout/Breadcrumb_cap_w.png

Run now status not updating after upgrade to K1000 v5.4

I recently upgraded my server and agents to 5.4. Now none of my scripts are updating to completed in the run now status.  They stay under the "scripts running" tab in the Run Now Status screen, and show "Status Unknown" when you view the Scripting Log under the computer inventory.  I did not have this problem on 5.3.  It even is happening for a simple registry change, that I have it log "completed" or "failed" when it is finished. 


0 Comments   [ + ] Show comments

Answers (4)

Posted by: diverdaveman1 11 years ago
Purple Belt
1

Dang-it!!! I spoke too soon. The solution for me was to enable 'Save All Agent Logs' after the upgrade. Go into the System UI (http://kbox/systemui), then Organizations, Organization tab, then at the bottom choose 'Save All Agent Logs'.

Don't forget you must enter 'Edit Mode' to make the change.

This solution got my scripts working

Posted by: BaldDragon 11 years ago
White Belt
0

Check your agent log retention under K1000 Settings: Agent. Set it to Save All Agent Logs.

If you had any errors during the upgrade, one of the steps is to disable it. This happened to me also.

Posted by: SMal.tmcc 11 years ago
Red Belt
0

I would contact support on this.  Have not seen this problem on our k1000 and have not seen a post on this on forum


Comments:
  • Just curious, but have you upgraded your clients yet? - diverdaveman1 11 years ago
  • some from 5.1 and some from 5.3, used provisioning - SMal.tmcc 11 years ago
Posted by: diverdaveman1 11 years ago
Purple Belt
0

I'm seeing the same thing. I run the script but nothing happens on the clients - new and old version clients.

 
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