Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Error concerning LDAPUserImporterImpl when importing data from LDAP onto Liferay

Written By

Neil Cuzon

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  •  We encountered the following error when attempting to import user data from LDAP onto Liferay: 

  •  ERROR [liferay/scheduled_user_ldap_import-1][LDAPUserImporterImpl:817] Unable to import user CN=firstName lastName,OU=STU,OU=UserAccounts,OU=Tier2,OU=COMPANY: null:null:{samaccountname=sAMAccountName: firstName.lastName}

    org.springframework.dao.DataIntegrityViolationException: could not update: [com.liferay.portal.model.impl.UserImpl#8695514]; SQL [update User_ set mvccVersion=?, modifiedDate=?, jobTitle=? where userId=? and mvccVersion=?]; nested exception is org.hibernate.exception.DataException: could not update: [com.liferay.portal.model.impl.UserImpl#8695514]

Environment

  • DXP 7.0

Resolution

  • The error above is caused by the character count for the 'jobTitle' value exceeding 100 characters. The max number of characters allowed for the JobTitle column is set to 100 characters, by default. The issue is resolved by reducing the characters contained in the Job title to 100 characters. 
  • Another option is to create and use Custom Fields. 
  • Thirdly, we would like to stress that increasing the SQL Column limit is inadvisable to resolve this type of issue, as it might cause upgrade issues further down the line. 
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?