EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB42205: "An error occurred during authentication. Please contact your administrator: LDAP Server error (19): Constraint violation." error message appears when connecting with LDAP authentication in MicroStrategy 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


"An error occurred during authentication. Please contact your administrator: LDAP Server error (19): Constraint violation." error message appears when connecting with LDAP authentication in MicroStrategy 9.x

SYMPTOM:
When trying to connect to the Intelligence Server using LDAP Authentication, the following error message is seen:
 
 


"An error occurred during authentication. Please contact your administrator: LDAP Server error (19): Constraint violation." 

 
CAUSE:
Typically, LDAP error 19 is returned at any time the supplied credentials violate the constraints defined within the LDAP server.  This error originates from the LDAP server and not Strategy.  Two common instances where this error can occur are:

  • Adding an attribute value that doesn't meet the size limitations.  For example, an attribute is defined with an upper size limit of 8 characters.  A constraint violation is thrown, if a value of '123456789' is entered.
  • Adding a second value to an attribute that only allows one value to be present. 

ACTION: 
At the connection stage, this is caused by the credentials for the authentication user.  For an individual user, it can happen at login. Verify that the correct user and password are used for authentication.
 
If the issue persists, request the LDAP Administrator check the credentials in the system.  If usernames or passwords are violating constraints, correct them appropriately.


Comment

0 comments

Details

Knowledge Article

Published:

April 14, 2017

Last Updated:

April 14, 2017