Hi,

Strange, you have many "duplicate key" issues.
As if youj already played the migration once.
But what is strange is that if you already migrated, you should also have errors in creation of new tables.

Can you explain the history of your installation and all migrations ?

Hi,

We have no history because of no more ProjeQtor administrator at all.
We can suppose that only the first installation (V11.0.0) has been done.

We can suppose this is the first update.
To update ProjeQtor as indicated in 'readme_install V12.2.3.txt', we placed the new version's zip file on SRV-APP in this location:
"C:wamp64wwwprojeqtorV12.2.3.zip"
Then we ran 7-zip -> Extract here.
This forced the replacement of the files/folders present inside the folder:
C:wamp64wwwprojeqtor

We then ran the ProjeQtor application in a browser and some basic tests were OK (creating new tasks, reading reports, saving imputation, ...).

What do these errors in the update log mean and how to remove these errors easily?
Thank you for your help

Hi,
The previous ProjeQtor administrator left and I'm trying to take over, I assume V11.0.0 is the initial installation.

As indicated in 'readme_install V12.2.3.txt',
to update ProjeQtor, we placed the new version's zip file on the server in this location:
"C:wamp64wwwprojeqtorV12.2.3.zip"
Then we ran 7-zip -> Extract here.
This forced the replacement of the files/folders present inside the folder:
C:wamp64wwwprojeqtor

After launching ProjeQtor in a browser, a few basic tests were all OK (creating a new task, reading reports, recording duration taken, etc.).

Thank you for your help in quickly removing these errors from the log.

Check DB for all errors logged.
For instance, when you have error on codeUPDATE `navigation` SET id=378 WHERE name='menuCriticalResources' and id>378;Check table navigation in db, and look for line with id=378
If this line has name='menuCriticalResources' , all is fine.
This was a double executed migration.

If id 378 exists but with another name, this may be due to previous double-migration.
This requires a further analysis of the DB.
I a sorry but then this analysis will be out of scope of this free support.
Possbily you can contact us for assistance service.