After downgrading from Data Center to Enterprise Edition, license does not match edition

SonarQube
1

We recently downgraded from the Data Center edition to the Enterprise Edition. We have successfully performed the downgrade and we can verify that we are now running the Enterprise Edition. We have also uploaded the Enterprise Edition license to our installation. We can verify in the footer of the UI we see “Enterprise Edition”, as well as seeing “Edition: Enterprise” under Administration > System.

However, when we send a new scan to be processed, we see the following error under the Background Tasks:

Analysis suspended. The license edition (Enterprise Edition) does not match the installation edition (Data Center).

This is happening 100% of the time and is consistent, this has happened all 3 times we have run a scan against this installation.

How can we solve this issue?

2

Hey there.

What version of SonarQube are you using?

3

The latest, 10.6

4

Hey James.

Is there any chance that you have your old DCE of SonarQube still connected to the database? That’s the only way I can imagine SonarQube getting “confused”.

5

Entirely possible - how would we ensure that wasn’t the case?

6

We have restarted all services on the machine. We now appear to be presented with arbitrary “Canceled” statuses on the Background Task for each job. There are no further details. sonar-scanner reports to have completed successfully on the local scan, but the background task simply says “Canceled”. How can we diagnose further?

7

This seems somewhat similar: Why was the task been cancel?

8

That post (specifically my response here) provides some guidance for checking connections on Microsoft SQL Server. Is that the DB you’re using?

You should be able to find more information about cancelled tasks in your ce.log

9

So unfortunately checking ce.log, we see the following error:

Task does not exist anymore: CeTask

To note, no one cancelled the task, the no one deleted the project, etc.

10

That is a tell-tale sign of multiple SonarQube instances being connected to one database.

11

Awesome, we’re using Postgres if you have a mechanism for checking those connections

12

I think this StackOverflow post is pretty comprehensive.

13

Just an update here - that worked! It turns out we had a remaining test instance that we had to terminate.

1 Like
14

You inspired me to write a new guide to make it easier to answer this question in the future (and so people can find the guide if they search the same errors).