Forum

Ask, reply and learn. Join the community of Akaunting.

New Discussion

Error after upgrade to 2.1.14

Brad Smith   ( User )

Commented 2 years ago

there is an error in the SQL now and i can recover from my midnight backup but lost 5 invoices
im now not updating for 1 week till i see this is stable

Mark Rhyne   ( User )

Commented 2 years ago

https://akaunting.com/forum/discussion/installation-update/upgrade-2113-error-page-not-found

I had to add the line APP_URL=
under APP_SCHEDULE_TIME="09:00"

And that fixed it.

Mark Rhyne   ( User )

Commented 2 years ago

Sorry unrelated issue ignore above.

Melda Melda   ( User )

Commented 2 years ago

Hello,

Please, make sure you've set the "APP_URL" value in the .env file, located in the root directory of your Akaunting installation:


APP_URL=https://my-domain.com/installed-folder


Of course, "my-domain.com" and "installed-folder" depends on your installation.

Best regards

Mark Rhyne   ( User )

Commented 2 years ago

No its a different error Melda.

Its got something to do with this merge
Merge pull request #2046 from burakcakirel/add-company-id-media-tables

If you look at the Image attached : https://imgur.com/EEdzO0I
ita a SQL issue with the table existing.

A google of the Errors seems to indicate a DROP might be needed, but I'm no coder.

Sorry if I'm no help.

Skullmasher   ( User )

Commented 2 years ago

Same here.

Felix   ( User )

Commented 2 years ago

500 Internal Server Error after upgrading. Cant even go dashboard

Jake Day   ( User )

Commented 2 years ago

The issue is in the migration script run while updating. To get it working after the upgrade, just add the company_id column to both your media and mediables table and you should be good to go.

Jader Augusto Wagner   ( User )

Commented 2 years ago

500 Internal Server Error after upgrading.


logs:

The command /usr/local/bin/php artisan update:finish core 1 2.1.14 2.1.13 failed.

Exit Code: 1(General error)

Working directory: /home/clauwagner/public_html/akaunting

Output:
================
Finishing update...
Application cache cleared!

In Connection.php line 678:

SQLSTATE[42000]: Syntax error or access violation: 1059 Identifier name et
y_prefixed_mediables_media_id_mediable_type_mediable_id_tag_primary is too
long (SQL: alter table `ety_prefixed_mediables` add primary key `ety_prefi
xed_mediables_media_id_mediable_type_mediable_id_tag_primary`(`media_id`, `
mediable_type`, `mediable_id`, `tag`))


In Connection.php line 471:

SQLSTATE[42000]: Syntax error or access violation: 1059 Identifier name et
y_prefixed_mediables_media_id_mediable_type_mediable_id_tag_primary is too
long




Error Output:
================

Skullmasher   ( User )

Commented 2 years ago

@Jake Day Thanks for pointing the way to a solution

I'm on .14 with tables modified as you said.

Yet still 500 errors.

Screenshots : https://imgur.com/a/pMEmLCW

Please login or register to leave a response.

Showing 11 to 20 of 38 discussions