Failed To Schedule Operation: 'No Connection Could Be Made Because The Target Machine Actively Refused It'

Version 4

    Symptoms

     

    The following error is received when attempting to schedule a scan

    Failed to schedule operation: 'No connection could be made because the target machine actively refused it'

    FailedtoSchedule.jpg

     

    Cause

     

    Another program or service is using the same port as the Shavlik Scheduler, stschedex.exe .  The default port assignment is 5120.

     

    Resolution

     

    1.  Change the port the used by the Shavlik Scheduler from 5120 to an available port on the target machines.  See How to change the default Scheduler Port

     

    2.  Identify the application or service that is using port 5120 on the target machine and change its listening port. Using the built-in  windows resource monitor, resmon.exe , is an effective way to identify what ports are being used on the system.  The file name of the St Remote Scheduler Service is StSchedex.exe.

     

    Affected Product(s)

     

    Protect 9.X