Task Scheduler stops triggering tasks between midnight and 1 am after Endpoint Protection 14.0 RU1 install.

Products

• Endpoint Protection

Issue/Introduction

Windows (2008 SP2) Task Scheduler stops triggering tasks between midnight and 1 am for an undetermined amount of time after Symantec Endpoint Protection (SEP) 14.0 RU1 Build 3752 was Installed

Task Engine "S-1-5-18:NT AUTHORITY\System:Service:" received a message from Task Scheduler service requesting to launch task "\Symantec Endpoint Protection\Symantec Endpoint Protection Error Processor" . 
Task Scheduler started "{89abf413-8537-4081-a9c0-0e2aa614f757}" instance of the "\Symantec Endpoint Protection\Symantec Endpoint Protection Error Processor" task for user "<username>". 
Task Scheduler launched "{89abf413-8537-4081-a9c0-0e2aa614f757}" instance of task "\Symantec Endpoint Protection\Symantec Endpoint Protection Error Processor" due to a time trigger condition. 
Task Scheduler launched action "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\SymErr.exe" in instance "{89abf413-8537-4081-a9c0-0e2aa614f757}" of task "\Symantec Endpoint Protection\Symantec Endpoint Protection Error Processor". 
Task Scheduler launch task "\Symantec Endpoint Protection\Symantec Endpoint Protection Error Processor" , instance "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\14.0.3752.1000.105\Bin\SymErr.exe" with process ID 5016. 

Environment

Windows 2008 SP2 

Symantec Endpoint Protection (SEP)

Cause

SYMERR task is the root cause taking 4-6 hours and not letting other tasks kick off

Resolution

Disable the SYMERR task, then all other tasks function fine.

The SYMERR task is part of SymQual, it sends data and crash dumps for processes up to Symantec to help make the product better. It will not impact the security or functionality of SEP if SYMERR is disabled.