1 Reply Latest reply on Feb 5, 2018 10:35 AM by cwinning

    Patching job does not start

    tompetro Rookie

      Hello all,


      Had a manually scheduled job in my schedule. It was supposed to start at 12:30 AM on a certain date. It did not start and shows nothing in the tracker. It is also out of the schedule.


      Two questions: Could this be caused if my primary hard drive on the server running the console was very low on disk space?


      Secondly, where do I go to see what happened to the job?? A log??



        • 1. Re: Patching job does not start
          cwinning CommunityTeam



          Low disk space on the console server could easily cause a deployment issue.  The logs are located in this folder: C:\ProgramData\LANDESK\Shavlik Protect\Logs  You could start with the ST.Protect.managed.Username@MachineName.log, scroll to the bottom if it was a recent deployment attempt.  Keyword to search for would be disk.