What does "Error (Log Upload Failed)" mean in the Current Phase of the schedule? (4293657)

What does "Error (Log Upload Failed)" mean in the Current Phase of the schedule?

See the error message "error (Log Upload Failed)" when looking at either:

1. The Security section under Device Details
   • Go to ​Inventory | Devices
   • Click on the Name of an affect machine
   • Scroll down to the​ Security section
   • Expand out Patching Detect/Deploy Status
   • Error is seen under Current Phase of Scheduled Task Status

OR

2. The Patch Tasks under Patch Schedule Detail
   • Go to Security | Patch Management | Schedules
   • Click on the Name of an affected schedule
   • Scroll to the bottom of the Patch Schedule Detail
   • Click [Show All] to show all the end points associated with this Patch Schedule
   • Error is seen under Patch Results

Error (Log Upload Failed) simply means the agent wasn't able to upload handshake, detect, deploy, verify, or rollback logs to the SMA Appliance.  Many times this happens when there is heavy traffic on the network.  Resetting patch tries then rerunning the schedule resolves most if not all of the messages.  KACE support won't be able to assist with checking network for bandwidth/speed or bottlenecks, but this article can help ensure the issue doesn't lie with the appliance.

Items to check:

• What time does the patch download take place?  Make sure the download has finished before other schedules are kicked off.  If assistance is required to determining this,  send in a screenshot of the Patch Download Setting, plus a screenshot of your Patch Download log. 
  • If Organizations are not enabled:
    From adminui
    • Go to Security | Patch Management | Patch Download Settings
    • Go to Settings | Logs
    • Click drop down and select Patch Download Log
  • If Organizations are enabled:
    From systemui
    • Go to Settings | Control Panel | Patch Download Settings
    • Click Settings | Logs
    • Click drop down and select Patch Download Log
  • If the Patch Download log is empty, gather the server logs:
    *See Obtaining Appliance (Server) Logs on a KACE Appliance (134230)
• Are detects running separately from patch deploys?  If so, make sure there is enough time for the detect to finish before the deploy kicks off.
• How far apart are are the Patch schedules?  Per best practices, make sure they are at least 1 hour a part. It's recommended to test with a small group of machines/patches to help troubleshoot the issue. Review article KACE SMA Performance Considerations and Best Practices (234057)

1. Enable debugging on a machine that is a good example of the issue if it's on version 6.4 or below. See How to enable debug logs on the KACE K1000 Client (112035)
2. Reset patch tries.  See How to reset the maximum deployment tries on a patch (116842)
3. Rerun the patch schedule.  Optional: In order to not disrupt current schedule setup, copy a patch schedule and run against the selected test machine.
4. Review your GPO settings to make sure that the agent is not being re-installed. Using an older version of the GPO Provisioning Tool causes the Kace Agent to be repeatedly re-installed (262376)
5. If the error continues to occur, gather the Kapture State logs and submit a ticket to support.  See How to Use the KACE Kapture State Utility for Windows (116144) and How to contact KACE Technical Support (111230)

__________

Is your KACE solution working as efficiently as possible? Learn more about our KACE Health Check.