Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Invalid login param...
 
Notifications
Clear all

Invalid login parameters after brand new install

15 Posts
2 Users
0 Reactions
8,530 Views
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 
[#5419]

Hello,

I have installed the latest version 7.2.2 and I can't login with admin/admin, it displays the error message:
Invalid login parameters

I tried to reinstall 3 times and I have always the same problem.

In the logs I have seen that it tries to look in projeqtor.user table that doesn't exists. It should look in ressource table.

/SqlElement.php:2371]
2018-09-13 12:13:09.875 ** ERROR ** [V0.3.0]    #1 SqlElement->getSqlElementsFromCriteria called at [/projeqtor/tool/loginCheck.php:67]
2018-09-13 12:13:09.875 ===== TRACE ===== Login error for user 'admin'
2018-09-13 12:13:10.030 ** ERROR ** [V0.3.0] Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'projeqtor.user' doesn't exist
2018-09-13 12:13:10.031 ** ERROR ***** [V0.3.0]    For query : select * from user where user.name='admin' and user.isUser = '1'
2018-09-13 12:13:10.031 ** ERROR ** [V0.3.0]    Strack trace :
2018-09-13 12:13:10.031 ** ERROR ** [V0.3.0]    #0 Sql->query called at [/projeqtor/model/persistence/SqlElement.php:2371]
2018-09-13 12:13:10.031 ** ERROR ** [V0.3.0]    #1 SqlElement->getSqlElementsFromCriteria called at /projeqtor/tool/loginCheck.php:67]

Here is the end of logs after the install:

2018-09-13 12:13:09.784 ===== TRACE ===== REWRITE PARAMTERS.PHP FILE = END ======================
2018-09-13 12:13:09.784 ===== TRACE ===== set default profile [V3.4.0]
2018-09-13 12:13:09.786 ===== TRACE ===== delete old references to projectorria [V4.0.0]
2018-09-13 12:13:09.787 ===== TRACE ===== update user password changed date [4.2.0]
2018-09-13 12:13:09.800 ===== TRACE ===== update bill reference [5.1.0.a]
2018-09-13 12:13:09.806 ===== TRACE ===== Create delivery types from deliverable types
2018-09-13 12:13:09.855 ** ERROR ** [] ERROR **
2018-09-13 12:13:09.855 ** ERROR ** [] on file */projeqtor/model/Cron.php' at line (266)
2018-09-13 12:13:09.855 ** ERROR ** [] cause = fopen(/RESTART): failed to open stream: Permission denied

PHP version 7.1.21
Everything was green but php max_input_vars is at 1000 and I can't modify php.ini (It is a web server with plesk and I don't have additional php settings)

Do I miss something at setup ?


 
Posted : 13 Sep 2018 14H31
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

Ensure that PHP user has write access to all flders (at least until install in complete)


 
Posted : 13 Sep 2018 14H36
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

I set the folder to 777 and I still get the same error:

/projeqtor/model/Cron.php' at line (266)
2018-09-13 12:52:49.679 ** ERROR ** [] cause = fopen(/RESTART): failed to open stream: Permission denied


 
Posted : 13 Sep 2018 15H00
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

check table cronexecution.
Welete line where functionName = 'cronImputationAlert'

It is an issue that is fiexed on patch 7.2.3 (to come)


 
Posted : 13 Sep 2018 15H05
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

Ok, I have
cronImputationAlertCronResource
cronImputationAlertCronProjectLeader
cronImputationAlertCronTeamManager
cronImputationAlertCronOrganismManage

but not cronImputationAlert


 
Posted : 13 Sep 2018 15H18
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

These are correct.

I set the folder to 777 and I still get the same error:

Recursively ?
Check that files/cron is 777


 
Posted : 13 Sep 2018 15H25
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

I have tried with 777 on cron folder, but I have the same error.
The log file was written so I thought it was not a write problem.

PS: I have install on a local WAMP Server with succes but it is a temporary solution.


 
Posted : 13 Sep 2018 19H25
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

OK, I got a reproduction case.

Delete all line in table cronexecution where
functionName starts with cronImputationAlert (at least 4 but you may have duplicates)
functionName is not set (emprty string or null)

it should work better then


 
Posted : 13 Sep 2018 20H40
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

I have deleted the lines in the DB, but I don't know what to do after as I can't login


 
Posted : 13 Sep 2018 21H12
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

remove file files/cron/MIGRATION
You should then be able to login.


 
Posted : 13 Sep 2018 21H29
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

it stills try to lgoin via user table


 
Posted : 13 Sep 2018 21H37
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

The fisrt error log should not matter.

Just to be sure, where is parameterValue for line of parameterCode='dbVersion' ?


 
Posted : 14 Sep 2018 10H54
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

Parameter value in parameter table for dbVersion is
1 NULL NULL dbVersion V0.3.0


 
Posted : 14 Sep 2018 16H54
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

I think this is source or your issue.

Drop all tables and reconnect.
(they will be regenerated)


 
Posted : 14 Sep 2018 17H15
 Ludo
(@ludm)
Posts: 8
Active Member
Topic starter
 

Thank you very much, I can log in ! 😉


 
Posted : 14 Sep 2018 17H43
Share:

Scroll to Top