nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot enter license for Jira Service Desk

Victor Peters

Jira Service Desk 4.4.3 was installed as an additional app on an existing Jira Software (Server) instance version 8.4.3 some time ago. However, the Jira Service Desk was NOT activated by NOT entering a license key.

Now the time has come to start using Jira Service Desk.

But I cannot find a location in the application to enter the license key. In the Applications > Versions & Licenses page there's no entry for the installed Jira Service Desk application.

Trying to re-install the same version of the application (*.OBR file) on that page results in an error message (stating that I have to view the logs to find out the reason is). Due to a lot of activity on the Jira Server instance it's almost impossible to find an entry in the logs that might give us a clue as to what caused the issue.

I'm hesitant to install a newer version of the Jira Service Desk application in our production environment. Removing the JAR files with "servicedesk" in the name in <JIRAHOME>/plugins/installed-plugins is also a risky operation, considering that it is our production environment.

Does anybody have an idea how to activate Jira Service Desk or safely remove it?

Accepted answers

All comments

Vickey Palzor Lepcha

Did you not find a place to paste the license from where you installed SD ?

I think there is a pencil icon that lets you add the license from where you can see SD installed.

Victor Peters

As you can see from the screenshot below, the Jira Service Desk application is nog listed under Applications > Versions & Licenses. So there's no pencil or input field related to that application that I could use to enter a license key.

Victor Peters

Using the "Upload an application" link on the page should enable me to re-install the application using the *.OBR file. But when I do that I get an error message that refers me to the logs on the server. Due to the large amount of users and the large amount of entries added to the logs each second/minute, it's almost impossible to find the exact log entry/entries that might explain what the error is. To also find of a solution to that error requires more in-depth knowledge of the software than I currently have.

Vickey Palzor Lepcha

Without looking at the log messages it would be tough to find out what error you are facing whole uploading SD application.

I'd suggest you reach out to Atlassian and share your logs with them. They will help you find out the solution.

Else if you wish to work on it - i'd suggest you to export out the log and do a text search to find the relevant log message at that time frame.

Having come to think of it - sort and find the error message based on the time when you upload and face error.

Victor Peters

Atlassian Support supplied us with a solution to our problem.

This solution required a (small) database update.

The following query on the Jira database revealed several modules/plugins with the property "pluginenabled" having the value "false":

SELECT * FROM pluginstate WHERE pluginenabled = 'false';

In order to enable the plugin, we had to perform the following database update:

update pluginstate set pluginenabled='true' where pluginenabled='false';

This essentialy sets the property to "true".

Before the update was performed, Jira had to be stopped / shut down and after the update Jira had to be started again to sort of 'pick up' the change in the database.

After the re-start of Jira the Service Desk application was listed (again) in de Applications > Versions & Licenses page and I was able to enter the license key for it.

Problem solved!

Vickey Palzor Lepcha

hmmm so basically a lot of related plugins/modules were disabled and it remained disabled.

I've had such cases in the past with other plugins - I either enabled them manually via browser or had the environment restarted with a longer restart time for plugins and its modules so that they get a good amount of time to restart.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server