How To Fix EG135 - Generic lock of devices to be changed failed

SAP Error Message - Details

• Message type: E = Error

• Message class: EG - IS-U device management

• Message number: 135

• Message text: Generic lock of devices to be changed failed

What causes this issue?

The system has tried several times without success to lock all devices
in the current client in order to add them to the lot.

System Response

The generic locks were not executed.

How to fix this error?

Check the following:
Does it make sense to execute a generic lock on the devices in order to
process the lot? In other words is the number of devices to be locked
high enough to warrant a generic lock?
Does it make sense to lock all devices in the system at this point in
time?
Only use the generic lock if the system is not being used by other
users.

Procedure for System Administrators

Plan jobs with generic locks for times at which the system workload is
minimal and no other users need to access the device data.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EG135 - Generic lock of devices to be changed failed ?

  The SAP error message EG135, which states "Generic lock of devices to be changed failed," typically occurs in the context of device management or when trying to change the status of a device in SAP. This error can arise due to various reasons, including issues with device locks, system configuration, or database inconsistencies.
  Causes:
  
  Device Locking Issues: The device you are trying to change may be locked by another user or process, preventing modifications.
  Database Inconsistencies: There may be inconsistencies in the database that are causing the locking mechanism to fail.
  Authorization Issues: The user may not have the necessary authorizations to change the device status.
  System Configuration: Incorrect configuration settings in the device management module can lead to this error.
  Network Issues: Temporary network issues can also cause communication problems with the database.
  
  Solutions:
  
  Check Device Locks: Verify if the device is currently locked by another user or process. You can use transaction codes like SM12 to check for locks and release them if necessary.
  Review Authorizations: Ensure that the user has the appropriate authorizations to perform the action. You can check this using transaction SU53 after the error occurs.
  Database Consistency Check: Run consistency checks on the database to identify and resolve any inconsistencies. This may involve using transaction codes like DB02 or DBACOCKPIT.
  System Configuration Review: Review the configuration settings related to device management to ensure they are set up correctly.
  Restart the Process: Sometimes, simply restarting the transaction or the SAP GUI can resolve temporary issues.
  Check for System Updates: Ensure that your SAP system is up to date with the latest patches and updates, as this can resolve known bugs.
  Contact SAP Support: If the issue persists, consider reaching out to SAP support for further assistance, especially if it appears to be a bug or a more complex issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to check locks), SU53 (to check authorization issues), and DB02 (for database monitoring).
  SAP Notes: Search for SAP Notes related to error EG135 in the SAP Support Portal, as there may be specific fixes or workarounds provided by SAP.
  Documentation: Review the SAP documentation for device management to understand the configuration and operational aspects better.
  
  By following these steps, you should be able to diagnose and resolve the EG135 error in your SAP system.