Event ID - 303

Event Id303
SourceMicrosoft-Windows-TaskScheduler
DescriptionTask Scheduler is shutting down the task engine "%1" due to an error in "%2". The error value is: %3.
Event Information According to Microsoft :

Cause :

This event is logged when task Scheduler is shutting down the task engine due to an error.

Resolution :

Use error code to identify the action failure

There has been a failure in the communication between the Task Scheduler service and an engine. Use the error code provided in the failure event to further identify possible reasons for the failure. The following list contains information about possible error codes. The problem may also have been transient.

Task Scheduler error codes:

SCHED_E_TRIGGER_NOT_FOUND
0x80041309
A task's trigger is not found. Try to edit the task's triggers.

SCHED_E_TASK_NOT_READY
0x8004130A
One or more of the properties required to run this task have not been set.

SCHED_E_TASK_NOT_RUNNING
0x8004130B
There is no running instance of the task.

SCHED_E_SERVICE_NOT_INSTALLED
0x8004130C
The Task Scheduler service is not installed on this computer.

SCHED_E_CANNOT_OPEN_TASK
0x8004130D
The task object could not be opened.

SCHED_E_INVALID_TASK
0x8004130E
The object is either an invalid task object or is not a task object.

SCHED_E_ACCOUNT_INFORMATION_NOT_SET
0x8004130F
No account information could be found in the Task Scheduler security database for the task indicated. Set the account information for the task.

SCHED_E_ACCOUNT_NAME_NOT_FOUND
0x80041310
Unable to establish existence of the account specified. Set the account information for the task.

SCHED_E_ACCOUNT_DBASE_CORRUPT
0x80041311
Corruption was detected in the Task Scheduler security database; the database has been reset.

SCHED_E_NO_SECURITY_SERVICES
0x80041312
Task Scheduler security services are available only on Windows NT.

SCHED_E_UNKNOWN_OBJECT_VERSION
0x80041313
The task object version is either unsupported or invalid.

SCHED_E_UNSUPPORTED_ACCOUNT_OPTION
0x80041314
The task has been configured with an unsupported combination of account settings and run time options.

SCHED_E_SERVICE_NOT_RUNNING
0x80041315
The Task Scheduler Service is not running. Start the Task Scheduler service.

SCHED_E_UNEXPECTEDNODE
0x80041316
The task XML contains an unexpected node.

SCHED_E_NAMESPACE
0x80041317
The task XML contains an element or attribute from an unexpected namespace.

SCHED_E_INVALIDVALUE
0x80041318
The task XML contains a value which is incorrectly formatted or out of range.

SCHED_E_MISSINGNODE
0x80041319
The task XML is missing a required element or attribute.

SCHED_E_MALFORMEDXML
0x8004131A
The task XML is malformed.

SCHED_S_SOME_TRIGGERS_FAILED
0x0004131B
The task is registered, but not all specified triggers will start the task.

SCHED_S_BATCH_LOGON_PROBLEM
0x0004131C
The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal.

SCHED_E_TOO_MANY_NODES
0x8004131D
The task XML contains too many nodes of the same type.

SCHED_E_PAST_END_BOUNDARY
0x8004131E
The task cannot be started after the trigger end boundary.

SCHED_E_ALREADY_RUNNING
0x8004131F
An instance of this task is already running.

SCHED_E_USER_NOT_LOGGED_ON
0x80041320
The task will not run because the user is not logged on.

SCHED_E_INVALID_TASK_HASH
0x80041321
The task image is corrupt or has been tampered with.

SCHED_E_SERVICE_NOT_AVAILABLE
0x80041322
The Task Scheduler service is not available.

SCHED_E_SERVICE_TOO_BUSY
0x80041323
The Task Scheduler service is too busy to handle your request. Please try again later.

SCHED_E_TASK_ATTEMPTED
0x80041324
The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition.

SCHED_S_TASK_QUEUED
0x00041325
The Task Scheduler service has asked the task to run.

SCHED_E_TASK_DISABLED
0x80041326
The task is disabled.

SCHED_E_TASK_NOT_V1_COMPAT
0x80041327
The task has properties that are not compatible with earlier versions of Windows.

SCHED_E_START_ON_DEMAND
0x80041328
The task settings do not allow the task to start on demand.

Verify :

Create a task for the user for which the task engine was failing, and ensure that the session events (events 301, 304, 308, 310, 312, 313, 314, 317, 318, 319, and 320) are received throughout session creation and shutdown. The events are logged in the in the Microsoft-Windows-TaskScheduler/Operational event log.

To define a task and register a task:
  1. Click the Start button and type Task Scheduler in the Start Search box.
  2. Select the Task Scheduler program to start Task Scheduler.
  3. Click Create Task .
  4. On the General tab, define a name for the task. On the Triggers tab, add a trigger to the task. On the Actions tab, define an action for the task.
  5. Click OK , and verify that no errors are reported when the task is created.
  6. Select the new task and verify on the History tab that there are not any partial registration failures for the task.
To verify that events are in the Task Scheduler event log:
  1. Click the Start button and type Event Viewer in the Start Search box.
  2. Select the Event Viewer program to start Event Viewer.
  3. Locate the Microsoft-Windows-TaskScheduler/Operational event log by expanding the Applications and Services Logs folder, expanding the Microsoft folder, expading the Windows folder, expanding the TaskScheduler folder, and then clicking the Operational event log.
  4. Verify that the session events are in the log.
Reference LinksEvent ID 303 from Source Microsoft-Windows-TaskScheduler

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh