Upgrade from 3.5 o 4.3.3 failed - Missing logininfo table

[Brad Lackey]

We are trying to upgrade our Confluence installation and rand into signifigant problems. This is hosted on Solaris with MySQL 5.5. We used the .zip file download, changed the conflience-init.properties and copied the JDBC driver. The problem is that wene we started the new instance, we geat an exception that the logininfo table is missing.

After brief searching, I wonder if this is a new table created after the upgrade?

What I didn't notice is where Confluence updated the schema/table info. How does this get triggered on a standalone install?

[Brad Lackey · Accepted solution]

It turns out that the upgrade instructions are correct! You must have installed your valid license befre doing the upgrade. After putting in my new license, all is well.

[Jobin Kuruvilla [Adaptavist]]

Could this be due to case sensitivity? Is the table there?

https://confluence.atlassian.com/display/CONFKB/Upgrade+Fails+%27java.sql.SQLException+Table+confluence.BANDANA+doesn%27t+exist%27+Due+to+Case+Sensitivity

[Bryce Johnson]

Did you make sure that you didn't upgrade from 2.5 straight to 4.3.3?

I had a problem upgrading from Confluence 3.3.1 to Confluence 4.2.X. I had to do it in multiple upgrades. Please make sure you do the right steps there. I had to first upgrade to 3.5.17 and when I did that I didn't have a non-crowd site admin user. Second upgrade was to 4.0.7.

So please try to review the upgrade notes found here:

https://confluence.atlassian.com/display/CONF43/Confluence+3.5+Upgrade+Notes

https://confluence.atlassian.com/display/CONF43/Confluence+4.3+Upgrade+Notes

https://confluence.atlassian.com/display/CONF43/Confluence+4.3.2+Upgrade+Notes

Here's a couple snippets from my support issue:

I then upgraded to 3.5.17. But alas, I couldn't login and couldn't create an non-crowd internal directory admin user (in 3.3.1) so I had to hack my database with:https://confluence.atlassian.com/display/DOC/Restoring+Passwords+To+Recover+Admin+User+Rights

After that upgrade I went to 4.0.7:

I then had to upgrade to 4.0.7, though 4.2.X was advertised upgrade path, because of crowd data issues.

You should then be able to upgrade to 4.3.X (at the time 4.2.X was only available).

[Brad Lackey]

It was actually 3.5 I typod' the subject. Thanks though.