Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Import of Jira users into Crowd fails due bad SQL grammar

tlmueller June 9, 2019

I get the following error when trying to connect JIRA 8.1 as an application in CROWD 3.4.5:


java.lang.RuntimeException: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [SELECT groupname from groupbase order by groupname]; nested exception is org.postgresql.util.PSQLException: ERROR: permission denied for relation configuration.pnggroupbase Location: File: aclchk.c, Routine: aclcheck_error, Line: 3410 Server SQLState: 42501

In the following links, there is (in my opinion) another reference to that problem:

Postgres config:

         Name   |  Owner   | Encoding |   Collate

jira | admin    | UTF8     | C.UTF-8     | C.UTF-8

  List of schemas

  Name  |  Owner   


public | postgres


Could anyone give me a hint, what I might do to resolve this import issue?



1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 11, 2019

Hi Timo,

It looks like you are running into a problem when trying to import these Jira users into Crowd.   Given the nature of your SQL error it looks like this is a SQL permissions issue though.

I can see in your screenshot that it looks like Crowd is trying to connect to the Jira database with a SQL username of 'crowd_support'.  However it looks like the jira database is owned by a SQL user named 'admin'.   So in this case, I would want to try to use the same SQL user that Jira is using when it starts up.  I think that would be this admin account, but if we're not sure, one quick way to see what Jira is using is to seek a peek at the


file.  This file holds the SQL database connection string that Jira uses to connect to that database when it starts up. I would try to use the username and password found in that file when you then have Crowd try to import that data.  This way we know when Crowd tries to do this import, it will be using the same SQL credentials that Jira uses to operate.

Please let me know if this helps, or if I have misunderstood some aspect of this problem here.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events