You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I had this problem solved in april and now is it back. The old thread was:https://community.atlassian.com/t5/Crowd-questions/Log-in-to-crowd-console-gt-Invalid-login/qaq-p/783269#M3180
Invalid Login and no sync with Azure Active Directory. Now with Crowd Version 3.2.1 and Java 1.8.0_172. A reinstall (with the same ApplicationData-Directory) was not successful.
In Logfiles are in
-..\apache-tomcat\logs\catalina.2018-05-30.log -> 0 Errors
-..\apache-tomcat\logs\crowd-stderr.2018-05-30.log -> 0 Errors
-..\apache-tomcat\logs\crowd-stdout.2018-05-30.log -> 2 Errors:
2018-05-30 11:24:37,732 localhost-startStop-1 WARN [tool.schema.internal.ExceptionHandlerLoggedImpl] GenerationTarget encountered exception accepting command : Error executing DDL via JDBC Statement
2018-05-30 11:51:40,940 Caesium-2-1 ERROR [atlassian.crowd.directory.DbCachingDirectoryPoller] Error occurred while refreshing the cache for directory [ 622593 ].
Have you an idea, what is to do?
MS Windows 2016 Server Datacenter in Azure VM
Azure SQL DB
Java jdk and jre 1.8.0_172
Ok, the three solutions were:
Modified the value of the key: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Apache Software Foundation\Procrun 2.0\Crowd\Parameters\Java
change last line from "-Dfile.encoding=UTF-8" to "-Dfile.encoding=UTF8"
This has taken some hours of tests, trial and error.
We had help from an experienced polish Atlassian Partner, who has created a similar system to reproduce the failure. The error was reproducable and then they worked with java stack traces to delimit the error-cause. They could find and fix it.
The problem could be occur on some other installations with crowd+azure directory since crowd version 3.1.1 - 3.2.1.
Hello @Saxess Software GmbH
For what it's worth, I've noticed that as of today Azure SQL does NOT belong to the list of supported databases for Crowd, whereas it is explicitly listed as supported for Jira and Confluence. Maybe Azure SQL is not supported at this time, that could explain the JDBC error you get.