Problem to upgrade

kimi99 · February 6, 2022, 3:39pm

Hello
I have a problem upgrading from openemr version 4.1.4
Sincerely

mdsupport · February 7, 2022, 4:12am

Sorry to hear that.

If you post maximum amount of information about steps and error(s), perhaps you may get some help here.

Best luck to you.

kimi99 · February 7, 2022, 2:22pm

I have the vesrion of openemr 4.1.4 and when I try to upgrade it to 4.2.0 I get an error message

stephenwaite · February 7, 2022, 2:50pm

hi @kimi99 , I think you have to patch to 4.1.11 before upgrading.

kimi99 · February 7, 2022, 2:57pm

how can patch it pls can you help me

stephenwaite · February 7, 2022, 3:00pm

https://www.open-emr.org/wiki/index.php/OpenEMR_Patches

https://www.open-emr.org/wiki/index.php/Old_Outdated_OpenEMR_Patches

kimi99 · February 7, 2022, 8:23pm

i found patch for 4.1.7 and it still the some problem

stephenwaite · February 7, 2022, 8:33pm

did you try this one?
http://www.open-emr.org/patch/4-1-1-Patch-14.zip

kimi99 · February 7, 2022, 8:38pm

I have test it and it shows the same problem

mdsupport · February 7, 2022, 9:30pm

Do you use any of the ippf functions? Looks like after the upgrade it is trying to apply ippf upgrade and the statement causing error has not been upgraded to the latest layout_options columns.

If you do not need ippf functions, try the following :

restore database
Using Admin login, turn off ‘Specific Application’ that is currently using IPPF.
Replace ippf_upgrade.sql by an empty file in case the sql_upgrade has that patch hardcoded.
Run the upgrade again.

If you do want ippf stuff. You could try changing the statement to format Insert Into layout_options(colnames) values (colvalues);. However that is probably start of some other errors. Can’t help you with those.

Best luck.

kimi99 · February 9, 2022, 10:15am

hay sir when i add an empty file i have this error

mdsupport · February 9, 2022, 3:47pm

If you read the messages, patch.sql was the last step of main database upgrade. That was successful.

The error is related to language translations you may have put in or were old. Collation conversions are very time consuming to debug and fix. If you are ok with EMR’s standard translations, you will find it faster to delete 2 lang_* tables and recreate them with standard version. Maybe someone here may knows a better way.

Before anything you should use english login and test if everything is working ok.

Best.