ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Protection Engine service stops unexpectedly during service start


Article ID: 198647


Updated On:


Protection Engine for NAS Protection Engine for Cloud Services


Symcscan simply will not start. Its status is disabled everytime After rebooting Windows, starting the service displays error 1053.


SPE 7.9.x or 8.x is installed

On Windows, the following error appears either as a dialog box within services.msc or in the Application Log of the Windows Event Viewer:

Windows could not start the Symantec Protection Engine service on Local Computer.

Error 1053: The service did not respond to the start of control request in a timely fashion.


To identify the specific error 

  1. Attempt to start the service for Protection Engine.
  2. Look at the next to last line in Symantec ProtectionEngineAbortLog.txt
  3. Search the BROADCOM KB for the matching error.
  4. If you are unable to find a match, open a support case for further assistance.
    To quickly assist, support will need you to supply answers to the following questions:
    - What Operating System is present?
    - What version of Protection Engine is installed?
    - What patches are applied to Protection Engine, if any?
    - What is the exact error on the next to last line in SymantecProtectionEngineAbortLog.txt?
    - Is the UI for SPE enabled?
    - Has Java JRE been updated recently?


To attempt to start the Protection Engine service

  • Do one of the following:
    • On Windows, within the services.msc (the Services console) right click on the Symantec Protection Engine service, then click Start
    • On Windows, at the cmd prompt, type:
      net start symcscan

    • On Linux, at the bash prompt, type:
      service SYMCscan start


To look for the most recent error in ScanEngineAbortLog.txt

  1. Do one of the following:
    • On Windows, at the cmd prompt, type:
      type SymantecProtectionEngineAbortLog.txt

    • On Linux, at the bash prompt, type:
      cat SymantecProtectionEngineAbortLog.txt | tail -2

  2. Look at the next to last line of output. For example: 

    <timestamp> 900 Unexpected exception thrown : XML file did not validate - configuration.xml         <--- The next to last line always contains the error related to the stop
    <timestamp> 0 Symantec Protection Engine is shutting down; logs may contain more information.  <--- Ignore the final line. it will always be the same

NOTE: In the example output above, the configuration.xml file is corrupt, preventing the start of the Protection Engine service. Usually, this sort of corruption occurs when you directly edit the .xml files which contain the configuration of SPE, instead of using xmlmodifier.exe. Support almost never sees this as a support case. Expect that your error and cause is different.




Additional Information

Other examples:

  • Error: 300 XML files did not validate : Error Validating D:\Program Files\Symantec\Scan Engine\configuration.xml. Element 'CloudName': This element is not expected. Expected is ( admin )
    Cause: User error during application of SPE hotfix 8.0.0 HF06. For steps. see 175834 

  • Error: 400 CSAPI Failed to initialize
    Cause: Multiple possible causes. Enable CSAPI logging, attempt to start service again, and look in csapi.log for more details.
    For CSAPI logging on Windows, see 157519. For Linux steps, see 164895

  • Error: 500 Logging failed to initialize : Unable to open file /opt/SYMCScan/log/SSE20200904.log..
    Cause: Lack of free space on the partition or lack of permissions. Linux? see 198845

  • Error: 600 Failed to create temporary directory : Could not create temporary work directory.
    Cause: Lack of free space on the hd partition or lack of permissions. Linux? see 198845

  • Error: 1400 Failed to initialize IPC Channel
    Cause: SPE not able to communicate with CAFAgent component which handles comms with central web console. See 174149