How To Fix LDAPRC019 - Restriction violated

SAP Error Message - Details

• Message type: E = Error

• Message class: LDAPRC - LDAP Interface Messages in C

• Message number: 019

• Message text: Restriction violated

What causes this issue?

The entry transferred to the directory was rejected by the directory.
The probable cause is that rules have been created in the directory
for the specified object class that the entry does not fulfill. For
example, required attributes may not be filled with values.

System Response

This is a reconciliation problem between the directory schema and the
mapping setting for the LDAP server.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Correct the mapping for the LDAP server. To obtain detailed information
about the cause of the problem, check the log files for the directory
server.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LDAPRC019 - Restriction violated ?

  The SAP error message LDAPRC019 "Restriction violated" typically occurs in the context of LDAP (Lightweight Directory Access Protocol) integration with SAP systems. This error indicates that a certain restriction or rule defined in the LDAP directory is being violated during an operation, such as an attempt to add, modify, or delete an entry.
  Causes:
  
  Schema Violations: The operation may be trying to add or modify an entry that does not comply with the LDAP schema. For example, it might be missing required attributes or trying to set an attribute to an invalid value.
  Access Control Restrictions: The user performing the operation may not have the necessary permissions to modify the entry or attribute in question.
  Attribute Restrictions: Certain attributes may have restrictions on their values (e.g., length, format) that are not being met.
  Object Class Violations: The entry being modified may not conform to the required object classes defined in the LDAP schema.
  
  Solutions:
  
  Check LDAP Schema: