Scheduled Task Manager Pops Error: -2080374779 - Upgrade Scheduler Now

Version 4

    Symptoms


    When trying to access a machines Scheduler under Manage > Scheduled Tasks the following error occurs:

     

    1-scheduler is unreachable.png

     

    [Window Title]
    Refresh Machine

     

    [Main Instruction]
    The scheduler on machine 'MACHINE-NAME' is not available. (Error: -2080374779)
    The list of jobs currently scheduled on the remote machine is unreadable.

     

    [Content]
    Upgrading the scheduler will allow you to view scheduled jobs.

     

    An associated error from the ST.TaskScheduler.Managed log file is:

     

    2013-09-09T20:25:18.3326001Z 0007 E GetJobs|System.InvalidOperationException: The scheduler on machine 'MACHINE-NAME' is not available. (Error: -2080374779)
      at ST.TaskScheduler.ThreadedSchedulerJob.GetJobs(ManagedMachineDetails managedMachine)
      at ST.TaskScheduler.ThreadedSchedulerJob.GetJobs(ManagedMachineDetails managedMachine, Boolean& schedulerAvailable)

      

    Cause

     

    This issue is caused by the Scheduler of the Protect Console being a newer version than the Scheduler files on the target machine. This often occurs when an upgrade of the console has occured.

     

    Resolution


    Choose to 'Upgrade scheduler now' to upgrade the necessary files on the target machine and re-establish a connection to the target machines scheduler and scheduled tasks.

    After selecting to Upgrade the Scheduler, assign credentials with local admin rights to the target machine to perform the action.

     

    2-set credentials.png

     

    Alternative Resolution


    In some situations the automated upgrade may fail. An associated error from the ST.TaskScheduler.Managed log file is:

     

    2013-09-09T20:26:19.9161224Z 0001 C Program.ApplicationThreadException|System.Security.Cryptography.CryptographicException: Key not valid for use in specified state.

     

      at System.Security.Cryptography.ProtectedData.Unprotect(Byte[] encryptedData, Byte[] optionalEntropy, DataProtectionScope scope)
      at ST.Core.StringExtensions.FromProtectedByteArray(Byte[] source)
      at ST.Data.Services.Credentials.UserCredential.get_Credential()
      at ST.TaskScheduler.LoadScheduler.CreateJob(MachineTreeNode node)
      at ST.TaskScheduler.LoadScheduler.BtnInstallClick(Object sender, EventArgs e)
      at ST.UI.Toolkit.KryptonButton.OnClick(EventArgs e)
      at ST.UI.UserControls.STButton.OnClick(EventArgs e)
      at ST.UI.Toolkit.KryptonButton.OnButtonClick(Object sender, MouseEventArgs e)
      at ST.UI.Toolkit.ButtonController.MouseUp(Control c, Point pt, MouseButtons button)
      at ST.UI.Toolkit.ViewManager.MouseUp(MouseEventArgs e, Point rawPt)
      at ST.UI.Toolkit.VisualControlBase.OnMouseUp(MouseEventArgs e)
      at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
      at System.Windows.Forms.Control.WndProc(Message& m)
      at ST.UI.Toolkit.VisualControlBase.WndProc(Message& m)
      at ST.UI.UserControls.STButton.WndProc(Message& m)
      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

     

     

    In this situation a manual uninstall/re-install of the scheduler on the target will be necessary.

     

     

    Uninstalling/reinstalling the Shavlik (ST) Remote Scheduler service on a single machine

    http://community.shavlik.com/docs/DOC-2222

     

     

    Note: If the issue exists on multiple machines, the following document can be followed to use a Custom Action to remove the Shavlik Remote Scheduler from all affected machines.

     

    Setting up the Custom Action to Remove the Remote Scheduler for Protect version 9

    http://community.shavlik.com/docs/DOC-23009