Hi guys,
We have just upgraded our test site from 7.2.2 to 7.5.3 following the correct pathway.
Having just successfully installed the 7.4.x to 7.5.3 package, when we now click on Administration > System > Upgrade Wizard > System Check > Next, we receive an error message stating, “Database failure. Please refer to suitecrm.log for details”.
I’ve attached a screenshot of the error message, along with the relevant log file (i think).
Would really appreciate it if someone could please take a look at the log and advise the best course of action to resolve the issue, thus allowing future site upgrades.
Thanks,
Ray.
Allo,
I might reproduce the migration path as my current version is also 7.2.2 (and no upgrade is supported in Godaddy where the app is hosted), and get back to you. My version is not a production but a test system, so not not worried or the result.
So, will start with the upgrade from 7.2.x to 7.3.2 then from 7,3.x to 7.4.3 and so on…
We are also hosting our site on GoDaddy, so will be interesting to see if you can replicate the same problem.
anyone willing and able to troubleshoot this with me?
For any database error message like this always do a Quick Repair & Rebuild and execute any generated SQL. If you continue to get that error after doing that then check your suitecrm.log. It will tell you what query is having trouble.
Hi eggsurplus,
I’ve followed the process you’ve outlined and the upgrade error still persists. I’ve reviewed (and attached) a copy of the error log file and whilst there are some references & warnings some icons, “[WARN] Image icon_UpgradeWizard_32.png not found”, I cannot see what is causing the error.
Are you able to review the attached and see what you can find?
Your log has a bunch of “MySQL server has gone away” messages. This is the problem and what you need to search on for fixing it. Here’s one result that may help: http://stackoverflow.com/questions/7942154/mysql-error-2006-mysql-server-has-gone-away
Thanks… I had a read through the link you provided and it appears the SQL setting, max_allowed_packet, is not set high enough. Unfortunately though we are on a shared hosting plan with godaddy, which i’m pretty sure makes it impossible to get access to the php.ini file to make the change.
At least you know the reason for the issues now. Hopefully you are able to find a resolution for it.