Ok, that means you have an other issue
Problem is LDAP is very generic, you need to give a lot more information like type of LDAP server, used schemata, …
At the end it usually comes down to debugging:
- add an error_log of what the ldap_modify is trying to set, eg. before here
- if there’s nothing directly suspicious, start with unsetting the first half of the entries and retry
- still failing, try the second half
- and so on, until you find which attribute and value is causing the problem
- check the schema of the attribute to find out what’s wrong with the value
- it could be all sort of things: not updatable, ACL issues, value is not allowed, …
- if you know what the problem is, it’s usually easy to fix
If you need help with figuring out what the problem between your LDAP and EGroupware is, we’re happy to help via our commercial support: https://www.egroupware.org/en/egroupware-support/
Don’t get me wrong, the support is for finding out what’s wrong, adding a fix to EGroupware code-base is not charged.
Ralf