/build/static/layout/Breadcrumb_cap_w.png

Script never finishes running

SMA version 12.0.149. I have a powershell script to look for an AD user group and add it to the local users group. Running the script manually on a device works properly and only takes a few seconds. Running it from Kace with Run Now to test it on the same device (after removing the local group), it never finishes running. It creates the script folder under C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots, but the script doesn't show up in the folder. I've double checked that the script is set up in SMA like several other PS scripts that run properly (with one caveat below). I've never seen this behavior before.

The one difference with this script is that it uses a credential instead of local system because it has to connect to AD. Even if that was the problem, I would expect the script to show up in the dependency folder and I would expect for it to time out if there was some other problem with the AD connection (eg, a bad password for the credential).

The run status has even survived the appliance update from 11 to 12 with a reboot.

Any ideas on what to do? If not, I'll open a ticket with Quest.



0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nioky 1 week ago
Yellow Belt
0

Hi,


Do you have any replication set ? If yes, make sure that the script has been sync by performing an inventory on concerned replicata.

Otherwise it should directly look for the file on the appliance so the file should be here.


Best regards,

Nioky

Posted by: IgorAngelini 6 days ago
Yellow Belt
0

Find the script id number on "C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots" or on the URL of the script

And then run:  "C:\Program Files (x86)\Quest\KACE\runkbot.exe [number] 0" as admin, see if this gets you the script log, and if it's any use.



Comments:
  • Thanks, Igor. I should have updated this to say that I found a problem with my script and I was able to run it successfully from the SMA after I fixed that. The new run shows up as completed in the Run Now status.

    However, the previous ones with the bad script still show up as Running in the Run Now status. Unless someone says otherwise, I'll chalk this up as a red herring in the console. I don't see any indication that it's impacting anything else in the SMA. - tpr 6 days ago
 
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