Protection engine service fails to start with "Error 1069: The service did not start due to a logon Failure."

Products

• Protection Engine for NAS

Issue/Introduction

Symantec protection engine (SPE) service fails to start with "Error 1069: The service did not start due to a logon Failure."

The issue may be observed after an upgrade.

Please refer : About retaining the service account when you upgrade to version 8.2.1

Environment

SPE Version : 8.2.1

Java Version : JRE 1.8 8u321

Cause

Possible causes are:

• The right to log on as a service is revoked for the Service account used to launch SPE service
• Incorrect password used
• Password corrupt

Resolution

If the right to log on as a service is revoked for the specified user account, restore the right by performing the following steps:

• Start the Local Security Settings MMC snap-in (secpol.msc)
• Expand Local Policies, and then click User Rights Assignment.
• In the right pane, right-click Log on as a service, and then click Security.
• Add the user to the policy, and then click OK.
• Close the Local Security Settings MMC snap-in.
• Start the SPE service.

If it still fails, check the credentials if entered correct or check for any access limitation with AD admin.

Additional Information

About retaining the service account when you upgrade to version 8.2.1

Changing the Service Logon Account Information