If you think all Jira Server installations/Jira Cloud migrations are equals, you are wrong…
Sometimes exists invisible errors/problems in the installation that probably wake up in a long time in the future. ( Or for example, when you try to renew the Atlassian license)
In this case we want to explain the famous case of the “Ugly licenses” (Called also the 4eced2fd-4329-40f1-ae63-930c55a366b4 licenses)
A healthy Jira must have a serial number like this XXXX-XXXX-XXXX-XXXX and not the aspect of 4eced2fd-4329-40f1-ae63-930c55a366b4…
Thanks to the Atlassian Technical support team, we have a solution for this. Just changing the value in the database
- Setting up a temporary instance to acquire the new Server ID.
- Run this query to get the new Server ID (XXXX-XXXX-XXXX-XXXX) from its database.
select * from propertystring where id in (select id from propertyentry where PROPERTY_KEY='jira.sid.key');
- Keep a full backup of your current database before applying the next query so that if anything goes wrong, you can restore it back.
- Stop JIRA.
- Update the Server ID to your current instance using the query below, replace the <SERVER_ID> with the new Server ID in the previous step:
UPDATE propertystring SET propertyvalue = '<SERVER_ID>' where id = (select id from propertystring where id in (select id from propertyentry where PROPERTY_KEY='jira.sid.key'));
- Restart your JIRA.
Many thanks to Benz