What does "Error (Log Upload Failed)" mean in the Current Phase of the schedule?
Symptom:
Error message:
"error (Log Upload Failed)"
when looking at Inventory > Computers > click on computer name > Security Section > expand "Patching Detect/Deploy Status" > "Scheduled Task Status"
Or
when looking at Security > Patching > Detect and Deploy Patches > select your Patch schedule > at the bottom click on [Show All] to show all the computers associated with this Patch Schedule
Did the Detection Phase complete and display results?
If there are no Patches to detect, then this is the resulting error.
Resolution:
You will want to make sure Patching has had a chance to finish downloading patches which normally happens at 3 AM.
Be sure you have selected a Label that has Patches applied to that same Patch Label used in the Patch Schedule.
Using best practice methods, you should have a Label for your Machines (example: Test Lab A) and another Label for your Patches (example: Patch - WinXP Critical Manual Deploy).
From the Patch Listing, select the patches you wish to detect and deploy and Apply the Label, "Patch - WinXP Critical Manual Deploly". Make sure this is the same Patch Label used in the Patch Schedule for the "Detect Patch Label Selection" (or enable "Detect All Patches") and "Deploy Patch Label Selection" Section.
Rerun your Patch Schedule and it should work.
Error message:
"error (Log Upload Failed)"
when looking at Inventory > Computers > click on computer name > Security Section > expand "Patching Detect/Deploy Status" > "Scheduled Task Status"
Or
when looking at Security > Patching > Detect and Deploy Patches > select your Patch schedule > at the bottom click on [Show All] to show all the computers associated with this Patch Schedule
Did the Detection Phase complete and display results?
If there are no Patches to detect, then this is the resulting error.
Resolution:
You will want to make sure Patching has had a chance to finish downloading patches which normally happens at 3 AM.
Be sure you have selected a Label that has Patches applied to that same Patch Label used in the Patch Schedule.
Using best practice methods, you should have a Label for your Machines (example: Test Lab A) and another Label for your Patches (example: Patch - WinXP Critical Manual Deploy).
From the Patch Listing, select the patches you wish to detect and deploy and Apply the Label, "Patch - WinXP Critical Manual Deploly". Make sure this is the same Patch Label used in the Patch Schedule for the "Detect Patch Label Selection" (or enable "Detect All Patches") and "Deploy Patch Label Selection" Section.
Rerun your Patch Schedule and it should work.
3 Comments
[ + ] Show comments
-
Same issues here, I've opened a call with Kace. Since the last Kbox patch I am getting this - FicmanS 10 years ago
-
I find this more and more. I spend a lot of time cleaning out the patches folder just to get patches up to date. If someone wrote a script to delete, I would appreciate if they would share. - anaccarato 9 years ago
-
Im getting this error as well. Suddenly. - lama01 5 years ago
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
