CSV User Import
This article provides assistance with problems importing user data via CSV files.
1. Check File Format
Problem | Symptom | Solution | System path |
|---|---|---|---|
Wrong separator | All values appear in a single column, certain values are not transferred, columns are not filled. |
| Import-specific configuration: User import planning function -> Description tab  |
Wrong character encoding | Umlauts / special characters are displayed incorrectly (e.g. ü instead of ü). |
| Global system configuration: Configuration function -> Import menu -> Description tab  |
2. Check Columns and Headers
Mandatory fields must be filled in and spelt correctly (e.g. LOGIN, EMAIL, etc.).
Column mapping is defined under Attribute mapping in the Description tab of the User import planning function.
sourceField = Column name
clixField = LMS personal attributeCODE<attributeMapping isReference="false" ignoreUnmappedFields="true"> <mapping sourceField="E-Mail-Adresse" clixField="LOGIN"/> <mapping sourceField="E-Mail-Adresse" clixField="EMAIL"/> <mapping sourceField="Nachname" clixField="LASTNAME"/> <mapping sourceField="Vorname" clixField="FIRSTNAME"/> </attributeMapping>
No empty mandatory fields
3. Perform Data Validation
Problem | Symptom | Solution |
|---|---|---|
Invalid email addresses | Import error | Check email format ( |
Duplicates | Multiple users | Remove duplicate entries |
Special characters in user names | Import denied | Check permitted characters (only letters, numbers, |
Relevant error codes and their meanings:
ID | Identifier | Comment |
PRS0001 | LOGIN_AUTHENTICATION_LOCKED_USER | User is marked as passive by authentication mechanism |
PRS0002 | LOGIN_AUTHENTICATION_MISSING_IDENTIFICATION | Username and password are missing for authentication |
PRS0003 | LOGIN_AUTHENTICATION_NO_MODULE | No other module present in sequence; user not authenticated |
PRS0004 | LOGIN_AUTHENTICATION_UNKNOWN_MODULEIDENTIFIER | Identifier for authentication module does not match any registered authentication module |
PRS0005 | LOGIN_AUTHENTICATION_MODULECAST | Casting exception when instantiating an authentication module; incorrect specification of classname |
PRS0006 | LOGIN_FAILED_CONNECTION | General connection error to authentication or profile data source |
PRS0010 | LOGIN_REGISTRATION_MISSING_REQUIRED_PROFILE_ATTRIBUTES | Not all mandatory profile data available during registration |
PRS0011 | LOGIN_REGISTRATION_EXCEEDED_LICENCE | Exceeding the permitted licences |
PRS0033 | LOGIN_REGISTRATION_LOGINNAME_UNKNOWN_TEMPLATEKEY | A key other than L, F, or N is used in the LoginName template |
PRS0038 | LOGIN_AUTHENTICATION_NO_UNIQUE_IDENTIFICATION | There are several users with the same login or the same login/password combination |
PRS0048 | LOGIN_REGISTRATION_LOGINCOMPLEXITY_INSUFFICIENT_LENGTH | Login is too short |
PRS0057 | LOGIN_PASSWORDCOMPLEXITY_NOT_ALLOWED_SYMBOL | Password contains invalid characters. Allowed special characters: !#$%&()*+,- |
PRS0063 | LOGIN_REGISTRATION_LOGIN_MISSING_LOGIN | No login name available |
PRS0064 | LOGIN_REGISTRATION_LOGIN_INVALID_CHAR | Login name with missing template contains invalid characters. Permitted special |
PRS0067 | LOGIN_REGISTRATION_CSV_FILE_NOT_FOUND | CSV file not found |
PRS0068 | LOGIN_REGISTRATION_CSV_IO_EXCEPTION | Error when accessing CSV file |
PRS0069 | LOGIN_REGISTRATION_CSV_INVALID_NUMBER_OF_RECORDFIELDS | Number of columns in a row does not match the title row |
PRS0070 | LOGIN_REGISTRATION_CSV_NO_COLUMNDEFINITION | Values in the first row could not be identified via parameter mapping |
PRS0071 | LOGIN_REGISTRATION_CSV_NO_IDENTIFER | Person identifier missing in column definition |
PRS0072 | LOGIN_REGISTRATION_CSV_PERSON_NOT_FOUND | Profile of the person searched for was not found in CSV file |
PRS0073 | LOGIN_REGISTRATION_CSV_UNIQUE_KEY_VIOLATION | Identifier of the person being searched for exists several times in the CSV file |
PRS0074 | LOGIN_REGISTRATION_CSV_MISSING_IDENTIFIER | Identifier of an entry in the CSV file is missing |
PRS0098 | LOGIN_AUTHENTIFICATION_DENY_OF_SERVICE | User blocked for login. Number of failed attempts was too high |
PRS0099 | LOGIN_AUTHENTICATION_NO_SELFREGISTRATION | Authenticated user cannot register himself because of conifg settings |
PRS0100 | LOGIN_REGISTRATION_NO_IMPORTSOURCE | No ProfileDataSource during user import has in config has isImportSource=true |
PRS0101 | LOGIN_REGISTRATION_PROFILEDATASOURCE_MODULEIDENTIFIERID | Id for profile data source does not match any registered profile data source |
PRS0102 | LOGIN_REGISTRATION_RULES_CONFIG_FILETYPE | File type for Rules Config upload invalid during user import |
PRS0104 | LOGIN_REGISTRATION_CSV_CONFIG_FILETYPE | File type for CSV Config upload invalid for user import |
PRS0105 | LOGIN_REGISTRATION_CONTENT_FILETYPE | File type for CSV upload invalid for user import |
PRS0107 | LOGIN_REGISTRATION_INVALID_CSV | Uploaded file does not contain a valid CSV |
PRS0109 | LOGIN_REGISTRATION_UNKNOWN_CLIXFIELD | ClixField in AttributeMapping is not a valid person attribute |
PRS0116 | LOGIN_REGISTRATION_EXCEEDED_ACTIVE_LICENSES | No more licences available |
PRS0117 | LOGIN_AUTHENTICATION_UNKNOWN_MODULEID | Id for authentication module does not match any registered authentication module |
PRS0118 | LOGIN_AUTHENTICATION_INVALID_USERMODE | AuthmodeId is identical to Id of module User |
PRS0119 | LOGIN_REGISTRATION_PROFILEDATASOURCE_PROFILEIDENTIFIER | Identifier for profile data source does not match any registered profile data source |
PRS0124 | LOGIN_REGISTRATION_CSV_DUPLICATE_COLUMN | Identifier of a column definition exists multiple times in CSV file |
PRS0127 | LOGIN_REGISTRATION_MISSING_SOURCEFIELD | Source field occurring in attribute mapping does not exist in import source |
PRS0128 | LOGIN_REGISTRATION_INVALID_CLIENTID | The ID of the root client does not appear in the list of mapped clients |
PRS0131 | LOGIN_REGISTRATION_INVALID_PERSONIDENTIFIER | One of the PersonIdentifiers specified in the config does not correspond to a Person DB field |
PRS0132 | LOGIN_REGISTRATION_IDENTIFICATION_FAILED_CLIX_UNIQUENESS | User identification for specified PersonIdentifier and search criteria within CLIX not unique |
PRS0134 | LOGIN_REGISTRATION_EMPTY_LOGIN | The login of a person to be stored is empty and the corresponding log generator |
PRS0137 | LOGIN_CONFIGURATION_NO_PERSONIDENTIFIER | There are no PersonIdentifiers in the profile data source of the person to be stored |
PRS0138 | LOGIN_REGISTRATION_MISSING_PERSONIDENTIFIER | The person to be stored lacks profile data-dependent PersonIdentifier attributes |
PRS0139 | LOGIN_REGISTRATION_UPDATEONLY_RESTRICTION | New person cannot be created, as according to the configuration for this profile |
PRS0140 | LOGIN_REGISTRATION_INSERTONLY_RESTRICTION | Existing person cannot be saved because, according to the configuration for this |
PRS0144 | LOGIN_REGISTRATION_COULD_NOT_STORE_PERSON_WITHOUT_ID | Internal page name error: Saving a person without person_id is not possible |
PRS0145 | LOGIN_LDAP_LOGINNAME_FAILED_UNIQUENESS | The login name to be authenticated is not unique on the LDAP system |
PRS0146 | LOGIN_CONFIGURATION_INVALID_IMPORTRESTRICTIONS | ImportRestrictions are not set uniquely in the config file |
PRS0147 | LOGIN_REGISTRATION_INVALID_EMAILADDRESS | Syntax of the email address is invalid |
PRS0148 | LOGIN_REGISTRATION_UNIQUEIDGENERATION_FAILED | UniqueIdGeneration for persons failed |
PRS0149 | LOGIN_READ_DEFAULT_VALUES_FAILED | Error in initialisation of default values for persons |
PRS0150 | LOGIN_READ_REQUIRED_FIELDS_FAILED | Error in the initialisation of the mandatory attributes for persons |
PRS0151 | LOGIN_REGISTRATION_NO_UNIQUE_IDENTIFIER | Identifier attributes of the current data source are not unique |
PRS0152 | LOGIN_AUTHENTICATION_CUSTOM_AUTHIMPL_FAILURE | Unexpected error within a custom AuthenticationModule implementation |
PRS0153 | LOGIN_REGISTRATION_LDAP_MISSING_IDENTIFIER | An attribute required for identification via LDAP is not included in the attribute |
PRS0154 | LOGIN_REGISTRATION_LDAP_EMPTY_IDENTIFER | An attribute in the mapping required for the LDAP profile data source is empty |
PRS0155 | LOGIN_REGISTRATION_RESOURCE_SYNCRONIZATION_FAILURE | An error occurred during the synchronisation attempt of the mapped resource person |
PRS0156 | LOGIN_REGISTRATION_USERID_FAILED_UNIQUENESS | The user ID of the person to be saved is not unique |
PRS0159 | LOGIN_MULTIPLE_RULES_VALID | Multiple rules valid |
PRS0181 | LOGIN_PERSON_MAP_ATTRIBUTE_VALUE | Error when assigning the value of an external attribute to a CLIX attribute |
PRS0187 | LOGIN_NAME_MAPPING_IMPLCAST | Implementation for LoginNameMapping cannot be instantiated |
PRS0188 | LOGIN_NAME_MAPPING_EMPTY_NAME | Implementation for LoginNameMapping returns NULL or empty string |
PRS0189 | LOGIN_NAME_MAPPING_GENERAL_EXCEPTION | General error for use in implementation for LoginNameMapping |
PRS0190 | LOGIN_NAME_MAPPING_TECHNICAL_PROBLEM | Technical error from external system, to be used in implementation for |
PRS0191 | LOGIN_NAME_MAPPING_TECHNICAL_PROBLEM_LEARNBASE | Technical error from external system Error text for Learnbase, to be used in |
PRS0193 | LOGIN_SECURITY_QUESTION_ANSWER | No answer to security question is given |
PRS0201 | LOGIN_NO_CLIENT_ID_CHANGE_ALLOWED | An attempt was made to change the client_id value for an existing user |
PRS0202 | LOGIN_INVALID_DATE_FORMAT | A date field has an incorrect format |
PRS0203 | LOGIN_REGISTRATION_MAPPING_MISSING_FILE | The defined attribute mapping file is not available |
PRS0204 | LOGIN_REGISTRATION_MAPPING_WRONG_FILE | The defined attribute mapping file has no valid content |
PRS0205 | LOGIN_REGISTRATION_LOGINCOMPLEXITY_MISSING_MAIL | Missing mail from login name |
PRS0206 | LOGIN_REGISTRATION_INVALID_DATE_VALUE | A date has an invalid timestamp format |
PRS0207 | LOGIN_REGISTRATION_INVALID_COSTCENTER_VALUE | The defined value for costcentre_id does not exist in the system |
PRS0208 | LOGIN_REGISTRATION_INVALID_USERTYPE_VALUE | The specified type_id is not supported by the system |
PRS0209 | LOGIN_REGISTRATION_INVALID_NUMBER_VALUE | The specified value must be a positive integer |
PRS0210 | LOGIN_REGISTRATION_INVALID_BOOLEAN_VALUE | The specified value is not valid for this field type |
PRS0211 | LOGIN_REGISTRATION_INVALID_SELECT_VALUE | The specified select_id does not exist in the system |
PRS0212 | LOGIN_REGISTRATION_INVALID_ATTRIBUTE_LENGTH | The given value is too long for that field |
PRS0213 | LOGIN_REGISTRATION_UNIMPORTABLE_CLIXFIELD | The import mapping contains attributes that are not allowed to change by import |
PRS0214 | LOGIN_USER_MARKED_AS_DELETED | The user is already marked for deletion |
PRS0306 | LOGIN_REGISTRATION_PHONENUMBER_INVALID | Phone number syntax is invalid |
PRS0307 | LOGIN_REGISTRATION_PHONENUMBER_MISSING_CODE | Country code missing |
PRS0308 | LOGIN_REGISTRATION_PHONENUMBER_UNKNOWN_CODE | Land pre-selection missing |
PRS0402 | LOGIN_EXTERNAL_REGISTRATION_NEEDED | Exception when a user must perform a self registration from external data |
PRS403 | LOGIN_AUTHENTIFICATION_NO_N_TIMES_NEW_PASSWORD | Exception when a user changes the password to a value it already had within the |
PRS404 | LOGIN_AUTHENTIFICATION_ERROR_ON_LOADING_PASSWORD_HISTORY | Exception when an error occurs while reading the password history |
PRS410 | LOGIN_FIRSTNAME_INVALID_CHAR | The attribute ‘first name’ contains invalid characters |
PRS411 | LOGIN_LASTNAME_INVALID_CHAR | The attribute ‘‘last name’’ contains invalid characters |
Best Practices
Always use UTF-8 without BOM
Write headers exactly as expected by the system
Before import: Clean up duplicates, special characters and blanks