Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

A consistent error while adding a new case

Gislain SODOGANDJI February 2, 2020

We consistently have the following error while adding a new case in Jira Software.

The case get added but the error always show up and the screen remains. You have to close it manually.

Could somebody help over this ? Thanks.

Une exception a eu lieu : com.atlassian.plugins.rest.common.json.JsonMarshallingException: org.codehaus.jackson.map.JsonMappingException: Caught SQLServerException for select ACTION.id, ACTION.issueid, ACTION.author, ACTION.actiontype, ACTION.actionlevel, ACTION.rolelevel, ACTION.actionbody, ACTION.created, ACTION.updateauthor, ACTION.updated, ACTION.actionnum from dbo.jiraaction ACTION where ACTION.issueid = ? and ACTION.actiontype = ? order by ACTION.created asc, ACTION.id asc offset ? rows fetch next ? rows only (through reference chain: com.atlassian.jira.quickedit.rest.api.field.QuickEditFields["createdIssueDetails"]->com.atlassian.jira.rest.v2.issue.IssueBean["fields"]->java.util.HashMap["comment"])

1 answer

1 accepted

0 votes
Answer accepted
Adrian Stephen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 2, 2020

Hi @Gislain SODOGANDJI  

Welcome to the community!

You might be using an unsupported database version which is causing this error. 

What is the Jira version and database type & version that you are using? 

Ensure that you are following the supported platforms page:

Gislain SODOGANDJI February 2, 2020

Hi @Adrian Stephen 

 

Thanks you for your quick reply.

Jira version is Jira Software 8.1.0

Database type is mssql

version : sqlsvr 2008 R2

Gislain SODOGANDJI February 2, 2020

I see that the database is not in the supported list.

Can we just update the database without any issues to the current installation of Jira ?

Adrian Stephen
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 3, 2020

Hi @Gislain SODOGANDJI 

Glad to hear that we found the root cause!

Yes, there should be no problem switching the database. 

You may follow the steps here:

Suggest an answer

Log in or Sign up to answer