Symptoms

• Scheduled Scan or Deployments fail.
• The following error may be seen in an event or within the scheduler.log from C:\Windows\Propatches\Scheduler on a target system:
  Error 10038: An operation was attempted on something that is not a socket.
• Within the ST.Protect.native log you may see an error such as the following:
  The service STSchedEx did not reach status Running within the specified time interval.
• You may see the following error message:
  The ST Remote Scheduler Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

Cause

StSchedEx.exe is attempting to listen on something other than the port specified in Protect Tools > Options > Scheduling. This is related to a known issue.

Resolution

This is a known issue that can occur in Protect 9.1.4334.0. This has been defected by Shavlik and should be fixed in the near future.

Workaround:

Go into Protect, Tools > Options > Scheduling and set the scheduling method to use the Microsoft Scheduler. This alternate method of scheduling will use the Microsoft Task Scheduler as a workaround.

Affected Products

Shavlik Protect 9.1.4334.0