KScript is failing to run or not completing as expected.
General Items to check for:
1. Under Configure is the Enabled box checked?
2. Under Deploy is the appropriate label selected? If so click on label name and verify the label is correctly set up and lists the machines that script applies to.
3. Make sure the Operating Systems section is correctly set up.
4. Is the schedule set up properly? If testing script selects none for the schedule to use the Save and Run Now setting to test upon saving.
5. Change the setting for On Failure to Continue.
Troubleshooting script Tasks.
1. Add message windows either before or after each step as needed to determine points of failure. For example to see if remediation step starts, create a message window alerting remediation start. Click Add under message window step and add a new step to run task remediation step such as launch a program. Save and click Add under this step, and add a new step to create a message window alerting remediation stop. When testing the script watch for message windows to see which task is starting or not, to point to the area of failure.
2. Change the Verify step to always fail to check if the verify steps are correct. If remediation steps now run the error is within the verification step.
Agent side troubleshooting steps:
1. Enable debug before the testing script. https://support.quest.com/kb/112035 (Note: SMA version 8.0 and higher have debugging automatically enabled).
2. Run the script from the K1000, using Save and Run Now.
3. To speed up testing open a command prompt and navigate to Program Files (x86) | Quest | KACE. Enter the command runkbot.exe 4 0, this will force the agent to check into the K1000 on command.
4. Watch for the script to run, looking for the message windows created previously. Watch for which message windows occur and which do not. Check for final product after the script is complete. If message windows fail to occur at certain steps check the step before for errors.
5. Check the files for the script within the K1000 agent folders, they are located at C:\Program Data\Quest\KACE. The log files are also located here. They are located in the user folder and called KAgent log. Please review the log for errors related to the script.
6. Look in Kbots_cache, packages, Kbots, find the script to make sure all files are downloaded. Can the script run manually from this location successfully? If so, check the run as settings on the script. Make sure account has permissions to run the packages on the system.
Before contacting support, ensure any software packages, batch files, or VBscripts can run stand-alone from the command line. If your package works we can help integrate it into a script. If after testing the issue persists, please run a KaptureState and provide logs and screenshots of script configuration to Kace technical support.
