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.

Symantec Protection Engine service fails to start with Windows error 1053

book

Article ID: 239046

calendar_today

Updated On:

Products

Protection Engine for NAS

Issue/Introduction

  • SPE server services are down.
  • When attempting to start the Symantec Protection Engine Service in the services.msc console, the following message appears:
    Error 1053: The service did not respond to the start of control request in a timely fashion.

  • The file SymantecProtectionEngineAbortLog.txt does not exist or does not log any new errors following an attempt to start the service.

Cause

Known causes:

  • Lack of system requirements.
  • Software corruption.

Environment

Release : 8.2.1

Component :

Resolution

  1. Confirm the presence of system requirements, This symptom is seen most frequently when SPE is installed on a machine with less than 4 CPUs.
  2. Do one of the following:
    • Trace through the behavior using the Sysinternals Procmon tool
    • Perform a clean install of Symantec Protection Engine

 

To perform a clean install of Symantec Protection Engine

  1. Backup the *.xml files from the C:\Program Files\Symantec\Scan Engine folder
  2. In the appwiz.cpl control panel, Uninstall Symantec Protection Engine
  3. Delete the folder C:\Program File\Symantec\Scan Engine
  4. Reinstall Symantec Protection Engine
  5. Re-configure from screenshots.