3357033 - Workaround for error: The user does not have permission: applocking, Action: logical_locking_create

Symptom

The following error is observed in the default traces:

500 Internal Server Error is returned for HTTP request [ ]:
component [ ],
web module [ ],
application [ ],
DC name [ ],
CSN component[ ],
problem categorization [ ],
internal categorization [ ].

[EXCEPTION]
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error occurred while servlet [ ] is initializing with a run-as identity.

Caused by: Initializing locking helper failed: The user does not have permission: applocking, Action: logical_locking_create

Caused by: java.lang.SecurityException: The user does not have permission: applocking, Action: logical_locking_create

Caused by: java.lang.SecurityException: User deploy_service is not authorized.

Caused by: java.security.AccessControlException: No authorization

Environment

SAP NetWeaver Application Server Java

Keywords

500 Internal Server Error, Action: logical_locking_create, Applocking, Application Locking, secure mode , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.