Protection Engine Service is not starting if running with custom user
search cancel

Protection Engine Service is not starting if running with custom user


Article ID: 273179


Updated On:


Protection Engine for NAS


The Symantec Protection Engine (SPE) service is not getting started if the SPE service is running with a custom user 

While starting the SPE service you can see the error "The Symantec Protection Engine service on the Local computer started then stopped".

In Windows Application Events you may see following error 
Date    Log    Event Type    Source    Computer    User    Event ID    Description    Details 8/31/2023 5:23:34 PM    Application    Error    Application Error    <Custom user details>        1000    "Faulting application name: symcscan.exe, version:, time stamp: 0x640b6917 Faulting module name: unknown, version:, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000001007017b8 Faulting process id: 0xfd4 Faulting application start time: 0x01d9dc01c4f3189c Faulting application path: D:\Program Files\Symantec\Scan Engine\symcscan.exe Faulting module path: unknown Report Id: 2b7189e0-b77e-4e79-b2eb-dc4fa5c57ac6 Faulting package full name:  Faulting package-relative application ID:"       SymantecProtectionEngineAbortLog.txt   2023/08/25-17:47:40 1600 Aborting with unknown message ID : Failed to start REST API service. 2023/08/25-17:47:40 0 Symantec Protection Engine is shutting down; logs may contain more information.



Symantec Protection Engine 9.0 and Higher


To run SPE service with a user other than 'SYSTEM', the user needs to have the privileges same as the Administrator.


Provide the Administrator Privileges to the custom user and start the SPE service.