Why are my scripting logs not getting uploaded to the K1000 appliance? (4293820)

Possible causes:

• Agent logging (retention) settings are turned off
• Scripting update has not yet occurred
• Logs are failing to upload to the K1000 appliance
• Script has not ran yet

Enable Agent Retention logs:

1. With Orgs enabled:
   1. From the K1000 Admin console, click the Organization drop-down box in the upper right hand corner and then click System.
      1. If fast-switching is not enabled and System is not an available choice, use the web URL to access the system level.   Example: http://kbox/systemui
   2. From the System org, Click Organizations | Name of desired org(s) and access selected org(s) details.
   3. Scroll down over to Communication Settings section.
   4. Check the 'Enabled' box under Agent Logging to enable the K1000 appliance to store scripting results provided by Agents installed on managed devices.
   5. Click Save
2.  Without Orgs enabled:
   1. From the K1000 Admin console, click Settings | Provisioning | Communication Settings
   2. ​Check the 'Enabled' box under Agent Logging to enable the K1000 appliance to store scripting results provided by Agents installed on managed devices.
   3. Click Save

Script XMLs and dependencies are stored in a subfolder of the KACE program directory. It is possible to ensure that the script XML and dependencies are downloaded to the system as expected.

Check if the script XML and dependencies are on the agent (system):

1. In Windows:
   1. Go to C:\ProgramData\Dell\KACE\kbots_cache
   2. Review this location to see if the XML exists for the script ID number
   3. Open the corresponding XML ID and review the tasks to ensure this is the correct script
   4. Go to C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\xxx (where xxx is the ID number of the script)
   5. Ensure that any/all dependencies have downloaded (if there are no dependencies, this directory may not exist)
2. In iOS:
   1. Go to /Library/Application Support/Dell/KACE/data/kbots_cache
   2. Review this location to see if the XML exists for the script ID number
   3. Open the corresponding XML ID and review the tasks to ensure this is the correct script
   4. Go to /Library/Application Support/Dell/KACE/data/kbots_cache/packages/kbots/XX (where XX is the ID number of the script).
   5. Ensure that any/all dependencies have downloaded (if there are no dependencies, this directory may not exist)

If the script XML and dependencies are downloaded, it is possible to review logs to see if the script ran successfully.

(Optional) Force the Script to Run:

1. In Windows:
   1. Open a CMD prompt by clicking on Start and typing CMD in search
   2. Navigate to the following directory:
      • If 32bit: C:\Program Files\Dell\KACE
      • If 64bit: C:\Program Files (x86)\Dell\KACE
   3. Use the following command:  runkbot X 0 (where X is the script ID number)
2. In iOS (Mac):
   1. Open Terminal by going to Launchpad | Other | Terminal
   2. Use the following command:  sudo /Library/Application\ Support/Dell/KACE/bin/runkbot X 0 (where X is the script ID number)

To review logs:

1. In Windows:
   1. Go to C:\ProgramData\Dell\KACE\user
   2. Open the KAgent.log with a text editor (eg. notepad.exe or notepad++)
   3. Scroll to the bottom (most recent event) or to the timestamp the script was run
   4. Review logs line by line for clues or possible errors
2. In iOS (Mac):
   1. Go to /Library/Application Support/Dell/KACE/data/user
   2. Open the KAgent.log with a text editor (eg. textedit)
   3. Scroll to the bottom (most recent event) or to the timestamp the script was run
   4. Review logs line by line for clues or possible errors

Example logs for script with ID 35:

If the above troubleshooting does not lead to clues about the script run, please contact support for assistance.  When opening a request with support, including the items below can help with a speedy resolution.

From the system:

• Turn on debugging and run your script again.
• If Windows: Run a Kapture State.
• If a Mac: Run a Kapture State.
• Be sure to include the script ID number in the report.

From the K1000 server:

• Screenshot of the script or an export of the XML (screenshot is preferred).
• Version of the KBOX Server.
• Version of the Agent.
• Time of the test.
• Screenshot of your Agent settings.