Hi,

Currently, my company's Window Server 2012 R2 job scheduler having a problem.

Then i found out the solution at http://support.microsoft.com/kb/2617046, so i download the hotfix to fix the problem.  However, i get another error as below.

Please, what can i do?

Thanks 

Best Regard

Vincent.

I knew the hotfix is for windows vista or windows 2008, however, i can't find any resources on window server 2012 R2.

Hi Vincent,

Since the hotfix should not be applicable to your system, I would suggest you check following conditions to troubleshoot the issue:

• The task was configured to run only when a specified network is available.
• The configured expiration time for the task has passed.
• The task is configured to ignore or queue a new task instance if a previous instance is still running.
• The task is configured not to run when the computer is on battery power.
• The task is configured to run only if a specific user is logged on.
• The task was disabled by a user.
• The previous task instance might have been running longer than expected because a component is busy processing data. If the task is normally expected to run for this length of time, consider modifying the task triggers to take this run-time length into consideration, or configure the task to be terminated after a preset time.

More information for you:

Event ID 322 Task Properties
https://technet.microsoft.com/en-us/library/cc727011(v=ws.10).aspx

Best Regards,

Amy

Amy,

Thanks for the tips, I follow the settings. I checked the condition and troubleshoot according to the lists you provided.

• The task was configured to run only when a specified network is available. (Not set this)
• The configured expiration time for the task has passed. (no expired time set)
• The task is configured to ignore or queue a new task instance if a previous instance is still running. (not set this)
• The task is configured not to run when the computer is on battery power. (yes, will not run when computer on battery power. will not happen because is a server all the time running AC power).

• The task is configured to run only if a specific user is logged on. (must select this, if not, the scheduler will not run at all)
• The task was disabled by a user. (is enabled)
• The previous task instance might have been running longer than expected because a component is busy processing data. If the task is normally expected to run for this length of time, consider modifying the task triggers to take this run-time length into consideration, or configure the task to be terminated after a preset time. (already set "Stop the task if runs longer than 3 days" and "If the running task does not end when requested, force it to stop".  and "Do not start a new instance " had been set)

Frankly, for the moment it run normally, somehow, I don't know when the incident will happen again.  It seem randomly happen, and not by default.  That is why kinda need the fix to fix this bug.  Cannot trigger email when this incident happen.  And the schedule we run is highly critical.

Thanks.

Hi Vincent,

Please let us know if the issue occurs in the future. We may need more information gathered by the time.

Since the task is highly critical, if the issue does occur again, I would suggest you try to place it on another server to see if it could get us more satisfying performance.

Best Regards,

Amy