Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Problem with Active Directory, LDAP, entries with umlauts

  • OhLove
  • OhLove's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 2 months ago #239784 by OhLove
Please help us help you and fill where relevant:
Your LimeSurvey version: Version 5.6.1+230123
Own server or LimeSurvey hosting: Own Server
Survey theme/template: fruity
==================

I have tried this with version 3.2.x as well but get the same error.
I have connected my Active Directory via LDAP, which works fine. But when I try to generate a userlist as soon as there is an entry with german umlauts (ä/ö/ü..) in the name, the process stops with500: Internal Server ErrorCDbCommand konnte das SQL-Statement nicht ausführen: SQLSTATE[22007]: Invalid datetime format: 1366 Incorrect string value: '\xE9' for column `limetest`.`lime_tokens_415467`.`firstname` at row 1
at first I thought it was an encoding/charset/collation issue, but the collation is utf8mb4_unicode_ci and the charset utf8mb4.
I can as well add manually an entry with umlauts into the table without a problem.

I tried dropping the database and create a new one filling it with php console.php install ... but that doesn't change a thing.

php mbstring is installed and active.

php version is 7.3, maridb is 10.3.36

Any idea or fix would be highly appreciated!

Thanks.

 

Please Log in to join the conversation.

  • OhLove
  • OhLove's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 2 months ago #239789 by OhLove
I just even tried a brand new installation on debian 11, php 7.4, mariadb 10.5.18 just to make sure it isn't any "leftovers" from previous updates with exact the same error message after importing users via ldap.

Please Log in to join the conversation.

  • OhLove
  • OhLove's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
1 year 2 months ago #240127 by OhLove
So after trying a lot of things I found out that I simply have to set LDAP version to v3.
technet.microsoft.com/en-us/library/cc755809(v=ws.10).aspx

It works now.

Please Log in to join the conversation.

Lime-years ahead

Online-surveys for every purse and purpose