Question [SOLVED] Kunena Internal Error: upgrade to 1.7, using jomsocial and jms multisite

Where is located the installed version when the installation packet check if i need upgrades? is there a version.xml or something similar? thanks

It's in database, can-i see the structure of your table jos_kunena_categories ?

before that i would like to explain you the situation.

Our site, www.thelastgames.net , is a social network based on joomla 1.5.25 plus jomsocial 2.04 and kunena forum.

The community needed to deploy multiple subsites for gamers teams and clans so we decided to use Joomla Multisite component (latest version installed 1.2.69)

All the other components upgrades was done easily, as described on extension upgrade instruction on jms guides.
The procedure needed to update components within all the network is this one:
1) install the new version of the component on the main site
2) install the new version of the component on every subsite (if there are database changes)

As Kunena changed some tables from 1.6.2 (the previous version that was installed on the site) and 1.7.1 i proceeded with the upgrade also on the slave site. When i did that it says the 1.7.1 version of kunena is already installed, but then i start having the issues described before.
I asked to you where is stored the component version to try a trick:
If i remove the latest version update from the database or wherever is stored i can proced with the upgrade in the slave sites. I tried also that way deleting the row where version 1.7.1 is stored in kunena_version, but when i tried to upgrade from the subsite it says again that the version installed is 1.71. Why is that? Do i need to change or delete something else to deceive the component doing the upgrade?

Kunena detects installed version from the database -- and DB is saying that it's already the latest (because of you already installed it). So if you're using only one database, you should be able to make Kunena to work just by running the installer in all sites, even if it says that it's already using the latest version.

So if multisite component works right, you should be able to get all sites working just by doing what the guide says -- and ignore what Kunena is saying during the installation.

The columns in the slave site are different that the ones in the main site, this is because the upgrade worked only on the main site. In the slave site the linked tables have still the old columns.

When I try to upgrade kunena in the slave site (to update the linked tables) it doesnt procede to the page where i can click on "upgrade kunena", also if i remove the row 1.7.1 in kunena_version table.

I need to upgrade linked tables in the slave site, how can i do it if i cant see the page where i can finde the upgrade button?

This is actually issue in your multisite component, as it should be able to handle conflicts that you get when using it. Kunena always uses the same database prefix and Joomla class to query -- it doesn't care where the database is located.

There's one exception that comes into my mind: If you share only part of Kunena tables and the rest are local -- that is when you get into troubles, at least during upgrade. You may try to disable site linking while you're upgrading the site (so the local tables gets created/updated), but that raises question: why do you want to share only some tables from Kunena?