Lost access to adminstrative/pull down functions

[Darrel Damon]

I have a 10 user instance of Confluence 4.3.1 on a local server.  I was given an evaluation key that would allow me to test out an upgrade to allow migration to confluence cloud.  I have run into issues with that and the evaluation key has since expired.

I'm not sure that this is related, but at about the same time the key expired, I lost the ability to use the pull down menus on my name or the "BROWSE" pull down menu.  Without this access, I cannot change keys even if I get a new evaluation key.

The questions are:

1. Could the lack of access be related to the expired evaluation key?

2. If so, how do I get in to change my key back to my original license key?

[Daniel Eads · Accepted solution]

Hi @Darrel Damon ,

Referencing some info from your previous question as well, as I see you replied with some info that slipped through my inbox.

For the license, it looks like the evaluation license you were granted is still valid for a couple more weeks (until August 19). The keys (both your current evaluation license, and your long-expired Starter license) should be available at my.atlassian.com for you to grab.

I'm doubtful just the license key is the reason for the troubles with dropdown menus. More likely this is related to upgrades, or restarting the application with some other errors in the install directory or with the plugin manager. There is a procedure for generating a license hash with a temporary install of Confluence on the same version, and then copying that value into Confluence's configuration file in its home directory.

I'm not convinced the license key is the direct problem for the issue you're seeing. The upgrade try is likely playing a role here. I'll be adding some more info on your previous question shortly.

Thanks,
Daniel | Atlassian Support

[Darrel Damon]

I found that the powers that be upgraded postgre without letting me know and it appears that this was the issue.  I had a backup and reinstalled 4.3.1 and tried to restore but it stalled at 40% and said it would take 2 days to complete.  I switched tracks and was able to install 4.3.7 and the restore took approximately 2 minutes to complete.

After that I tried the direct upgrade to 5.10 and got multiple errors with data base version mismatches.  I'm currently in the process of upgrading stepwise and I'm currently at 5.0.  I did try the upgrade from 5.0 to 5.10 and it appeared to be successful but I could not bring up data so I'm going to continue the steps.

It's been a journey. :)

[Daniel Eads]

Ah yes, an unsupported database change would do it! 

Confluence 4.2 thru 5.6 support Postgres 9.0. Once you hit Confluence 5.7, you'll need to upgrade to Postgres 9.2 in order to continue up to Confluence 5.10. Here's my recommended Confluence/Postgres upgrade path from where you're at:

1. Ensure you're on Postgres 9.0 currently
2. Upgrade from Confluence 5.0 to Confluence 5.6
3. Upgrade Postgresql to 9.2
4. Upgrade Confluence to 5.10
5. Run the Confluence Cloud Migration Assistant

Let me know if you get stuck anywhere along the way! We're here to help.

Cheers,
Daniel

[Darrel Damon]

Almost there.  I've completed the upgrade to 5.10.9 and have installed the migration assistant.  Last step is getting with the cloud admin and setting up time to go through the process with them.

Some questions have come up.  First, we will need to extend our trial license since I don't anticipate that I will get cloud to assist with the complete migration before the current expiration date.  Do I just request another trial license from the my.atlassian page?

Second - I'm assuming that the migration assistant will allow us to import spaces into an existing site without wiping out the existing site.  Does it accomplish this using xml backups of the space? I noticed that there is no longer a space admin place in 5.10.9 and I was looking to see if I could back up individual spaces.

Thanks for all your assistance to this point.  You have been very helpful and instrumental in getting me as far as I am.