AnsweredAssumed Answered

Upgrading an old version of SugarCRM CE

Question asked by dmcmulle dmcmulle on May 14, 2015
Latest reply on May 15, 2015 by dmcmulle dmcmulle
Hello.  Currently I have SugarCRM CE 5.2.0i installed on my webserver.  I tried to use the .zip file from sourceforge to upgrade from 5.2.0i to 5.5.0beta1 (SugarCE-Upgrade-5.2.0-to-5.5.0beta1.zip), and I am having some issues.

It seems the upgrade is stuck in some sort of loop.  The Admin->Upgrade Wizard page is currently returning an http/500 internal server error.  Upon further investigation, I see the following lines in my upgradeWizard.log:

Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - found a file with a differing md5: [./include/Dashlets/DashletGenericConfigure.tpl]
Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - found a file with a differing md5: [./include/Dashlets/DashletGenericChartConfigure.tpl]
Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - found a file with a differing md5: [./include/CurrencyService/CurrencyService.php]
(There are lots of these md5 errors)

And then:

Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - md5 verification done.  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - file preflight check passed successfully.  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - starting schema preflight check...  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - looking for schema script at: /var/www/sugarcrm/cache/upload/upgrades/temp/oS6Ts7/scripts/520_to_550_mysql.sql  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - found schema upgrade script: /var/www/sugarcrm/cache/upload/upgrades/temp/oS6Ts7/scripts/520_to_550_mysql.sql  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - schema preflight using MySQL  Thu, 14 May 2015 13:40:11 -0400 [UpgradeWizard] - schema preflight done.
Then, it seems the process stops for about 15 minutes, and then resumes calculating md5 checksums again (thus reporting more errors).  It seems the upgrade is stuck in some kind of infinite loop.  The log file is just expanding with what I've included above over and over with the exact same output.  

What can I do to remedy this?  We have 6 years of important information stored in sugar, and we cannot afford to lose that.  Yes, we have a database backup and file backup of sugar_crm.

Should I check the php logs?  Someone give me some advice on how to go about resolving this issue.

Thanks

Outcomes