windows scheduler : second task erroring out event id 111: Task stopping due to timeout reached

venkatesh padmanabhan 181 Reputation points

I have setup a windows scheduler ( windows server 2012 R2 version ) with a schedule of Daily at 6 a.m. and with repeat task of every 8 hours.
The first task does not show any error. However, most of the times the second task fails with error.
Event id : 111 .
Task stopping due to timeout reached.

In windows scheduler , for the task :
under conditions below are checked :
Power : start the task only if is in AC Power
stop if computer switches to battery power

stop if the computer ceases to be idle

under settings below are checked :

stop task if runs longer than 3 days

How to fix this ?

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
11,163 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Jasreet Singh 171 Reputation points

    Since its unclear what the scheduled task is for and expecting the server to be behaving based on load distribution during the day.

    First task runs at 6 a.m (Last for 3 days)
    Second time it runs at 2 PM (Last for 3 days)
    Third time it runs at 10PM (Last for 3 days if running)

    Assuming the load to be based on day time when users are most active, would like to ask you to check the performance of the system during the said interval that second task is assigned for and validate the logs for the task ID initiation date/time and stopped date/time to avoid multiple instance or resource locking issue.

    Please also try manually running the task during the day time and check the status of the task before starting it manually.

    We expect the load or multiple instances be the reason for the task to be causing the failure.

    0 comments No comments

  2. Limitless Technology 43,316 Reputation points

    Hi venkateshpadmanabhan-5594,

    There is one more condition to check that you haven’t mentioned:

    The task was configured to stop when a new instance of the task is triggered.

    Please check this under the task’s settings and see if that prevents the 111 event.

    I hope this answers your question.

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments