View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - Blocking PB migration 6.1.0 to 6.1.2 - Page 4 - ProjeQtOr
 

Blocking PB migration 6.1.0 to 6.1.2

More
20 Mar 2017 08:29 #19 by pipobru
Replied by pipobru on topic Blocking PB migration 6.1.0 to 6.1.2
Same database, without change.
after pb just for test i have tested with postgesql 9.5 and a empty database with this protocol:
Create new databe in 6.1.0 (without data)
Test migration to 6.1.2
=> same result (and same error)
The question is why migration crash but all other records running normally ?

Please Log in or Create an account to join the conversation.

More
22 Mar 2017 08:46 #20 by babynus
Replied by babynus on topic Blocking PB migration 6.1.0 to 6.1.2
I hs a look again at error, and it seems Database is not identified as Postgres.
Error on line 144 in Sql.php : this line should be reached only for MySql database.
Check in /tool/parametersLocation.php where you stores parameters.php file
Check your parameters.php file, it should contain $paramDbType='pgsql'
Babynus
Administrator of ProjeQtOr web site
The following user(s) said Thank You: pipobru

Please Log in or Create an account to join the conversation.

More
24 Mar 2017 08:13 #21 by pipobru
Replied by pipobru on topic Blocking PB migration 6.1.0 to 6.1.2
I have check and all parameters are OK:
$paramDbType = 'pgsql';
$paramDbHost = '127.0.0.1';
$paramDbPort = '5432';
$paramDbUser = 'pgsql';

Please Log in or Create an account to join the conversation.

More
25 Mar 2017 16:51 #22 by babynus
Replied by babynus on topic Blocking PB migration 6.1.0 to 6.1.2
check if 'pgsql' is owner of your database.
Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
27 Mar 2017 11:26 #23 by pipobru
Replied by pipobru on topic Blocking PB migration 6.1.0 to 6.1.2
I have check and same error ....
2017-03-27 11:22:37.847 ===== TRACE =====
2017-03-27 11:22:37.847 ===== TRACE ===== =====================================
2017-03-27 11:22:37.847 ===== TRACE =====
2017-03-27 11:22:37.847 ===== TRACE ===== DataBase actual Version = V6.1.0
2017-03-27 11:22:37.847 ===== TRACE ===== ProjeQtOr actual Version = V6.1.2
2017-03-27 11:22:37.847 ===== TRACE =====
2017-03-27 11:22:37.847 ===== TRACE ===== =====================================
2017-03-27 11:22:37.847 ===== TRACE =====
2017-03-27 11:22:37.847 ===== TRACE ===== VERSION V6.1.1
2017-03-27 11:22:37.847 ===== TRACE =====
2017-03-27 11:22:37.908 ***** ERROR ***** EXCEPTION *****
2017-03-27 11:22:37.908 ***** ERROR ***** on file '/var/www/html/testvide/model/persistence/Sql.php' at line (144)
2017-03-27 11:22:37.908 ***** ERROR ***** cause = SQLSTATE[55000]: Object not in prerequisite state: 7
2017-03-27 11:22:37.908 ***** ERROR ***** => #0 /var/www/html/testvide/model/persistence/Sql.php (144) -> lastInsertId()
2017-03-27 11:22:37.908 ***** ERROR ***** => #1 /var/www/html/testvide/db/maintenanceFunctions.php (71) -> query()
2017-03-27 11:22:37.908 ***** ERROR ***** => #2 /var/www/html/testvide/db/maintenance.php (101) -> runScript()
2017-03-27 11:22:37.908 ***** ERROR ***** => #3 /var/www/html/testvide/tool/loginCheck.php (135) -> include()

Please Log in or Create an account to join the conversation.

More
27 Mar 2017 14:37 #24 by babynus
Replied by babynus on topic Blocking PB migration 6.1.0 to 6.1.2
It seems you are running migration from V6.1.0 to V6.1.2 for database that already received upgrade to V6.1.1...
This is not blocking with MySql but seems more serious with pgSql.
Try and remove reference to this script on line 42 of db/maintenance.php.
from
"V6.0.0", "V6.0.2", "V6.0.3", "V6.0.6", "V6.1.0", "V6.1.1");
to
"V6.0.0", "V6.0.2", "V6.0.3", "V6.0.6", "V6.1.0");
Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

Moderators: babynus, protion
Time to create page: 0.047 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.

Login Form