Hi,
I have setup V5 and tried to migrate from V4 in its settings > Account management , migrations and it went well and got the following message
"
Migration has started. We’ll update you with status, on your company e-mail."
It’s been around 8 hours and no migrated data is being shown in V5.
Wondering how much time migration would take or is anything else that I may also try or check pls ?
Same problem here, from shared hosted server to shared host server with company details equal to old v4. I traced back the problem to this:(REMOVED is some personal details i had removed)
[2020-11-27 06:43:38] production.ERROR: Symfony\Component\Debug\Exception\FatalThrowableError [0] : /data/sites/web/REMOVED/app/Services/Migration/CompleteService.php [Line 54] => Type error: Argument 1 passed to App\Services\Migration\CompleteService::companyKey() must be of the type string, null given, called in /data/sites/web/REMOVED/app/Http/Controllers/Migration/StepsController.php on line 189 {“context”:“PHP”,“user_id”:1,“account_id”:1,“user_name”:“REMOVED”,“method”:“POST”,“user_agent”:“Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.67 Safari/537.36 Edg/87.0.664.47”,“locale”:“nl”,“ip”:“REMOVED”,“count”:1,“is_console”:“no”,“is_api”:“no”,“db_server”:“mysql”,“url”:“migration/companies”} []
So i Tried to replicate my v4 app on ubuntu local server, imported the sql installed laravel and website is running great local, but migration give another error of ‘forge’@localhost user not allowed.
I really want migration to work so i can make my invoices again, i can use the old version for now but hope to find the answer here…
Can you check your logs, please? You can find them in “storage/logs/laravel.log”. Also, in case you are unsure about what to look for, just PM them to me, here on the forum.
Also, what’s the value of QUEUE_CONNECTION in the .env file?
Also since our V5 is running good so is it possible that we manually dump mysql database of V4 into V5 so that the data appears in V5? Is it possible or we must have to do it via migrations in settings from our pannel only ?
I am a Senior Server Admin and deployed and migrated Invoice Ninja several times up to V4 version but this V5 migration is giving us hard time. Per your recommendations below is what we did plus some other things which we have tried too
So we have upgraded to your new version of V4 ( [v4.5.23) and tried the migration again but still there is same issue and migration never happens despite the message that “The Migration has Started Successfully” and we never see that in our V5 .
Also, There is no any QUEUE_CONNECTION entry in .env but through some research we tried to put QUEUE_CONNECTION=sync but that did not work too.
Below are the log files of V4.5.23 and V5.0.25
Also, as a side note that on our V5 it says to enable cron jobs which we have already did but it still shows the same message for enabling crons, not sure if that may cause the migration ?
cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1
Also, Health Check of V5 shows that all is good
![V5-healthcheck-forceupdate|269x312](upload://57blvAKwj6b5KM90X6lACBMGVwd.jpeg)
We tried to force update V5.0.25 and it said we already have latest version but even we forced update it just to make sure or fix any minor updates etc and it went well.
![v5-update|434x216](upload://qtIyHgIofi5sEIrm1YhlwpYCtez.jpeg)
Your assistance in this regard is highly appreciated. Thank you
Do you want to try clearing the v4 error log and trying again. I don’t think the error shown is from the latest release, its date is from before the release was available. It would be useful to know if the v4 side of the migration is completing without errors.
There is not any commented code which needs to be uncommented, Please clarify , or pls end me updated file here so that i can directly upload it to my system. Thanks
For the self update to work, you would have need to either clone the repo. OR use the invoiceninja.zip file from the releases. These two options contain the .git history.
If you install from Docker or if you just copy the regular release.zip’s these don’t have the git history so won’t be able to use the self update mechanism.