Fatal error with Upgrade Wizard before upgrade.

[DanyC]

Goog morning,

I'm trying to upgrade the Sugar version I have (5.2.0i) to 6.2 version. When I click on "Upgrade Wizard", it takes a while to load and then the following error appears:

"Warning: require_once(cache/upload/upgrades/module/project_Container...restore/custom/modulebuilder/packages/Container/zips/...12009_02_05_143523-manifest.php) [function.require-once]: failed to open stream: No such file or directory in E:\wamp\www\CRM_test\modules\UpgradeWizard\uw_util s.php on line 789

Fatal error: require_once() [function.require]: Failed opening required 'cache/upload/upgrades/module/project_Container...restore/custom/modulebuilder/packages/Container/zips/...-manifest.php' (include_path='E:\wamp\www\CRM_test\include/..;.;C:\php5\pear') in E:\wamp\www\CRM_test\modules\UpgradeWizard\uw_util s.php on line 789"


Looking for the line in the corresponding file, it says:

" require_once($target_manifest);"


Does anyone know if there's any way I can resolve this? I've been googling around, but I haven't found any useful answer. Any help is very welcome.

Thank you!

[Chris_C]

Just a guess - 5.2 is too far behind 6.2.

Try upgrading to 5.5, then to 6.0, 6.1, and finally to 6.2.

And as always, backup your live system first, in case there's a failure that renders it unusable, so you can restore it and try again in case there's any problem.

Also, you could test it out on a clone of your system before doing it on the real thing.

[DanyC]

I know. The plan is doing it step by step and all the security measures are already taken, but I don't even get to select the file. Instead of being redirect to the ' System Check', I inmediatly get the error I posted earlier.

Is it possible that it has something to do with an old module? Because when I check the module uploader to delete the old modules (this one, the 'project_container' in particular), I get a new error:

Fatal error: require() [function.require]: Failed opening required 'modules/paq1_Items/paq1_Items.php' (include_path='E:\wamp\www\CRM_test\include/..;.;C:\php5\pear')
in E:\wamp\www\CRM_test\modules\Administration\Rebuil dRelationship.php on line 78



Thank you very much for your answer!

[Angel]

You'll definitely need to perform your upgrade in steps as Chris mentions and with regards to the errors, it seems like you might have some sort of permissions issue.

Set the permissions on the cache directory to 755, recursively, and try it again.

[DanyC]

I'll try that then and I'll let you know how it work.

Thank you very much for your answers!

[Chris_C]

I'll try that then and I'll let you know how it work.

Thank you very much for your answers!

What Angel said is important.

Also, have a look at the solutions in the following thread, posts #7 and 8:

http://www.sugarcrm.com/forums/f115/...-5-2-0c-45796/

[kbrill]

Goog morning,

I'm trying to upgrade the Sugar version I have (5.2.0i) to 6.2 version. When I click on "Upgrade Wizard", it takes a while to load and then the following error appears:

"Warning: require_once(cache/upload/upgrades/module/project_Container...restore/custom/modulebuilder/packages/Container/zips/...12009_02_05_143523-manifest.php) [function.require-once]: failed to open stream: No such file or directory in E:\wamp\www\CRM_test\modules\UpgradeWizard\uw_util s.php on line 789

Fatal error: require_once() [function.require]: Failed opening required 'cache/upload/upgrades/module/project_Container...restore/custom/modulebuilder/packages/Container/zips/...-manifest.php' (include_path='E:\wamp\www\CRM_test\include/..;.;C:\php5\pear') in E:\wamp\www\CRM_test\modules\UpgradeWizard\uw_util s.php on line 789"


Looking for the line in the corresponding file, it says:

" require_once($target_manifest);"


Does anyone know if there's any way I can resolve this? I've been googling around, but I haven't found any useful answer. Any help is very welcome.

Thank you!

OK, I dont think this is a permission error, try this.

1) backup your database, specifically upgrade_history
2) truncate upgrade_history;
3) Try the upgrade again

This will make it so that SugarCRM wont care about old upgrades (which are not reversible anyway)

[DanyC]

Thank you all for your help. It turned out to be that the upgrade couldn't be done because of an old module that was broken (I hadn't installed it so I really don't know what happened or if it'd ever worked). We had to remove the modules from the folder where they were installed and then we were able to upgrade.

Again, thanks!

[Chris_C]

Thank you all for your help. It turned out to be that the upgrade couldn't be done because of an old module that was broken (I hadn't installed it so I really don't know what happened or if it'd ever worked). We had to remove the modules from the folder where they were installed and then we were able to upgrade.

Again, thanks!

Thanks for posting back your solution Dany! Welcome to 6.2 !

[gregbaskind]

Thanks for posting back your solution Dany! Welcome to 6.2 !

I just wanted to add a comment on pre-upgrade cleanup of a SugarCRM CE 5.2.0k

If you get something like:
PHP Fatal error: require_once(): Failed opening required 'modules/Feeds/Feed.php' (include_path='D:\sugarcrm\include/..;.;C:\php\pear') in \sugarcrm\modules\Administration\repairDatabase.ph p on line 111

Then it means that a standard of installed module's folder (modules/Feeds/Feed.php) either does not exist (was deleted) or has a corruption.

I would assume that if you have installed a module through Module Loader and it put a folder into /modules/
which got deleted or corrupt, you would also get
PHP Fatal error ....
repairDatabase.php on line 111.

Solution is to replace the folder from a clean copy.
You may have to install the same verison of SugarCRM (5.2.0.k) and then re-apply package custom package/extension.
Then you can copy the missing or corrupt /modules/xxxxx folder form the fresh/clean instance to your broken instance.

Dont forget to fix any permissions discrepancies between the replaced folder and others around it with something like
/modules# chown -R "you_systems_apache_user" /modules/xxxxx
and
/modules# chmod -R 664 /modules/xxxxx

Hope this helps others.