Re: Migrating from Jahia 4.0.7 to Jahia 4.1.1

Hi Pierre,

sorry for this late reply.

there seems to be a problem during the migration, but it is not related
specifically to the4.0.7 -> 4.1.1 migration. Obviously there is a
problem when with mssql server when we try to migrate the slide tables in
the dabatase to slide 2. We will try to reproduce the problem
internally.

Michel

Hi Michel,

I did try to intall the upgrade patch but it endend with an error
message:

java.sql.SQLException: There is already an object named 'jahia_sl2_uri'
in the database.java.sql.SQLException: There is already an object named
'jahia_sl2_uri' in the database.

What can I do next?

I attached to this message the log files created during the upgrade
process.

Thank you for your help,

Pierre Lemieux.

At 05:08 20-01-2006, you wrote:

Hi Pierre,

the upgrade patch which is available in the download area to migrate to
version 4.1.1 can be used to migrate version 4.0.6 or greater to 4.1.1,
so it will also work to migrate 4.0.7 to version 4.1.1, as indicated by
the phrase "only from Jahia >= 4.0.6" in the download panel.
I agree some indication in the download panel may be confusing, we will
try to make things clearer.

The following indication is also displayed in the readme file of the
4.1.1 upgrade patch :

"This patch can be applied either to Jahia 4.0.6, 4.0.7, Jahia 4.1.0
or 4.1.0_01. It will upgrade your Jahia installation to
4.1.1_01."

Or maybe you have encountered unexepected problem when trying to apply
this patch ?

best regards,

Michel Romy

Hello,

last week I upgraded our TEST server from Jahia 4.0.5 to 4.0.7_01 using
the upgrade script found at
http://www.jahia.net/jahia/page584.html . After a few days of testing
we decided to install version 4.0.7_01 on our production server also. I
installed it and it works fine on both servers now.

Yesterday I tried to upgrade our TEST server from 4.0.7_01 to 4.1.1 using
a migration script. It didn't work because the script only works with
version 4.0.6. What can I do now? Am I stuck with version 4.0.7_01? Or
can you provide us with a new script to upgrade from 4.0.7_01 to
4.1.1?

Another solution would be to go back to version 4.0.5 and then upgrade to
4.0.6 and to 4.1.1. I saved a copy of our 4.0.5 installation files but if
I have to restore the database (MS SQL) to the state it was before the
upgrade I will lose one week of work.

Do I have to restore the database if I go back from version 4.0.7_01 to
version 4.0.5?

Thanks in advance for your help,

Pierre Lemieux, bibliothèque de l'Université
Laval