- 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.
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 in Protect 9.1.4334.0.
This is a known issue that can occur in Protect 9.1.4334.0. This issue should be resolved in Protect 9.1, Patch 1 (9.1.4446.0).
Bug fix description from version history log/release notes of Patch 1:
Resolved an issue where STSchedEx would attempt to listen on an additional legacy port that is no longer being used. Will only attempt to open 5120 (default) and not open 5120 and 5121.
You can get the installer for Protect 9.1, Patch 1, here:
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.
Shavlik Protect 9.1.4334.0