New Migration Pack from Sugar CE to Suite 7.6

theersin · 1 May 2017 14:22

installer.log
EMPTY

suitecrm.log
I dont have SuiteCRM yet. Am I supposed to install it first? I am trying to upgrade sugarcrm

php_errors.log…

UpgradWizard.log

Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - File uploaded to upload://SugarCE Migration 6.5.x to Suite 7.1.8.zip
Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - extracting manifest.
Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - validating manifest.php file
Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - finding new files for upgrade
Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - *** Potential error: patch found with either no ‘type’ or non-patch type [ upload://upgrades/module/Event_Manager2014_03_10_170340.zip ]
Mon, 01 May 2017 13:36:44 +0000 [UpgradeWizard] - *** UW using [ ] as source for patch files

pgr · 1 May 2017 14:26

What’s that Event manager thing? A module you have? Could that be causing problems in your upgrade?

I assume that package (Event_Manager2014_03_10_170340.zip) is not what you’re trying to upload to get the upgrade done, but it seems to be interfering. You might find that file is a leftover in your upload/upgrades directory.

theersin · 1 May 2017 14:53

Event manager is a module that I created and I need to keep it. How can I avoid this error then?

pgr · 1 May 2017 14:58

The honest answer is “I don’t know”, I’ve never been through a migration like yours.

But you can try things. Like exporting the module, doing the upgrade, then importing it on the new system.

You could start by just trying to remove that package from that directory, I don’t think it’s necessary there… your real module files are elsewhere, I believe.

theersin · 1 May 2017 15:48

Just to try, I created a clone and deleted the module from sugarcrm completely and also removed event_module_zip. Now it goes on a loop…

Finished database permissions check.
Mon, 01 May 2017 15:16:31 +0000 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 15:16:31 +0000 [UpgradeWizard] - At upload.php
Mon, 01 May 2017 15:16:31 +0000 [UpgradeWizard] - finding new files for upgrade
Mon, 01 May 2017 15:16:31 +0000 [UpgradeWizard] - *** UW using [ ] as source for patch files.
Mon, 01 May 2017 15:17:39 +0000 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 15:17:39 +0000 [UpgradeWizard] - At upload.php
Mon, 01 May 2017 15:17:39 +0000 [UpgradeWizard] - running upload
Mon, 01 May 2017 15:17:59 +0000 [UpgradeWizard] - File uploaded to upload://SugarCE Migration 6.5.x to Suite 7.1.8.zip
Mon, 01 May 2017 15:17:59 +0000 [UpgradeWizard] - extracting manifest.
Mon, 01 May 2017 15:17:59 +0000 [UpgradeWizard] - validating manifest.php file
Mon, 01 May 2017 15:17:59 +0000 [UpgradeWizard] - finding new files for upgrade
Mon, 01 May 2017 15:17:59 +0000 [UpgradeWizard] - *** UW using [ ] as source for patch files.
Mon, 01 May 2017 15:19:54 +0000 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 15:19:54 +0000 [UpgradeWizard] - At upload.php
Mon, 01 May 2017 15:19:54 +0000 [UpgradeWizard] - running upload
Mon, 01 May 2017 15:20:30 +0000 [UpgradeWizard] - File uploaded to upload://SugarCE Migration 6.x to Suite 7.6.6.zip
Mon, 01 May 2017 15:20:30 +0000 [UpgradeWizard] - extracting manifest.
Mon, 01 May 2017 15:20:30 +0000 [UpgradeWizard] - validating manifest.php file
Mon, 01 May 2017 15:20:30 +0000 [UpgradeWizard] - copying manifest.php to final destination.
Mon, 01 May 2017 15:20:30 +0000 [UpgradeWizard] - zip file moved to [SugarCE Migration 6.x to Suite 7.6.6.zip]
Mon, 01 May 2017 15:32:14 +0000 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 15:32:14 +0000 [UpgradeWizard] - At upload.php
Mon, 01 May 2017 15:32:14 +0000 [UpgradeWizard] - finding new files for upgrade

Chrome stopped working and I forced to quit. I tried to continue…

on, 01 May 2017 16:36:48 +0100 [UpgradeWizard] - at preflight.php
Mon, 01 May 2017 16:36:48 +0100 [UpgradeWizard] - unzipping files in upgrade archive…
Mon, 01 May 2017 16:39:05 +0100 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 16:39:05 +0100 [UpgradeWizard] - at preflight.php
Mon, 01 May 2017 16:39:05 +0100 [UpgradeWizard] - unzipping files in upgrade archive…
Mon, 01 May 2017 16:41:32 +0100 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 16:41:32 +0100 [UpgradeWizard] - at preflight.php
Mon, 01 May 2017 16:41:32 +0100 [UpgradeWizard] - unzipping files in upgrade archive…
Mon, 01 May 2017 16:43:48 +0100 [UpgradeWizard] - setting session variables…
Mon, 01 May 2017 16:43:48 +0100 [UpgradeWizard] - at preflight.php
Mon, 01 May 2017 16:43:48 +0100 [UpgradeWizard] - unzipping files in upgrade archive…

No response…

pgr · 1 May 2017 15:54

If you have a clone and can experiment more aggressively, I would try completely removing (or renaming) “upload/upgrades” and starting over.

I believe you have some sort of old interrupted upgrade process lurking in the past of your system… and it’s coming back to haunt you.

theersin · 1 May 2017 16:19

nothing has changed! Still same errors.

I have SugarCRM 6.5.22 but the zip file I am trying is 6.x. As you said, maybe there is a corrupt file somewhere…

I don’t know what else to do, thanks anyway.

pgr · 1 May 2017 16:22

Hhmm I think you should be using a different file.

See at the very bottom of this page:

https://suitecrm.com/download?tmpl=component

theersin · 1 May 2017 16:32

I tried the SugarCE Migration 6.5.x to Suite 7.1.8 file before, it says “not compatible with you version of SugarCRM”. Thats why I was trying to make the other one work…

pgr · 1 May 2017 16:37

There’s a workaround for that here:

https://suitecrm.com/forum/installation-upgrade-help/6037-upgrade-to-7-3-fails-with-message-the-uploaded-file-is-not-compatible-with-this-version-of-sugar-sugarcrm-system-version-6-5-22

These latest SugarCRM versions seem to be just security patches. They were probably released after the SuiteCRM Upgrade package was last worked on. That’s probably why it doesn’t know about them and refuses to install, but you should be alright hacking it…

theersin · 1 May 2017 17:16

After I manually changed the version, now I have this!

Sugar CRM 6.5.20 Files May Only Be Used With A Sugar CRM 6.5.20 Database.

I have been trying to update the DB version as well but doesnt seem like editing is an option for me.

schnellbgl · 25 March 2018 17:24

I am running sugarcrm 6.5.26 on Windows and tried to migrate to suitecrm with the migration file “sugarCE 6.5.x to suiteCRM 7.1.4”. When trying to upload I get the message: “The uploaded file is not compatible with this version of Sugar: SugarCRM System Version: 6.5.26” as already mentioned earlier in this post.

Is there finally a solution to overcome this problem?

pgr · 25 March 2018 17:33

I can’t get this sorted out on the weekend but if you are technically resourceful you might look for a manifest or a config file inside the upgrade package, limiting which versions are allowed or not. You can try tweaking this and see if the upgrade works.

So you would unzip the package, tweak the file, zip it back, try the upgrade.

Of course, start by doing proper backups of all files and database, and proceed at your own risk, this is risky territory.

schnellbgl · 26 March 2018 14:43

Thank you very much. This was the solution

pgr · 26 March 2018 14:50

I opened an Issue for this here

https://github.com/salesagility/SuiteCRM/issues/5599

BTW, which file did you change?

schnellbgl · 28 March 2018 12:17

Sorry, I posted in the wrong thread. I tried to upgrade with the 6.5.to 7.1 package, which failed during upgrade. Have now tried it with the 6.5 to 7.6 package. Everything went with the wizard until the step commit upgrade. Here the upgrade process stops with an error message “database failure”. In the sugar log the following message is displayed

[spoiler]

03/28/18 11:10:31 [3680][1][FATAL] Array
(
[module] => Calls
[action] => index
[ajax_load] => 1
[return_action] =>
[return_module] =>
[Calls2_CALL_ORDER_BY] => date_start
[select_entire_list] => 0
[Calls2_CALL_offset] => 60
[show_plus] =>
[assigned_user_name] =>
[assigned_user_id] =>
[date_start] =>
[parent_type] => Accounts
[parent_id] =>
[parent_name] =>
[status] =>
[direction] =>
[searchFormTab] => advanced_search
[query] => true
[name_advanced] =>
[parent_type_advanced] =>
[parent_name_advanced] =>
[current_user_only_advanced] => 0
[status_advanced] => Array
(
[0] => Planned
)
[assigned_user_id_advanced] => Array
    (
        [0] => 1
    )

[showSSDIV] => yes
[saved_search_name] => 
[search_module] => 
[saved_search_action] => 
[displayColumns] => 
[hideTabs] => 
[orderBy] => DIRECTION
[sortOrder] => ASC
)

03/28/18 11:30:59 [3680][1][FATAL] Array
(
)

03/28/18 11:31:11 [3680][1][FATAL] Array
(
[module] => Calls
[action] => index
[ajax_load] => 1
[loadLanguageJS] => 1
[return_action] =>
[return_module] =>
[Calls2_CALL_ORDER_BY] => date_start
[select_entire_list] => 0
[Calls2_CALL_offset] => 60
[show_plus] =>
[assigned_user_name] =>
[assigned_user_id] =>
[date_start] =>
[parent_type] => Accounts
[parent_id] =>
[parent_name] =>
[status] =>
[direction] =>
[searchFormTab] => advanced_search
[query] => true
[name_advanced] =>
[parent_type_advanced] =>
[parent_name_advanced] =>
[current_user_only_advanced] => 0
[status_advanced] => Array
(
[0] => Planned
)
[assigned_user_id_advanced] => Array
    (
        [0] => 1
    )

[showSSDIV] => yes
[saved_search_name] => 
[search_module] => 
[saved_search_action] => 
[displayColumns] => 
[hideTabs] => 
[orderBy] => DIRECTION
[sortOrder] => ASC
)

03/28/18 11:31:20 [3680][1][FATAL] Array
(
[lvso] => asc
[Calls2_CALL_ORDER_BY] => date_start
[Calls2_CALL_offset] => 90
)

03/28/18 11:31:23 [3680][1][FATAL] Array
(
[lvso] => asc
[Calls2_CALL_ORDER_BY] => date_start
[Calls2_CALL_offset] => 90
)

03/28/18 11:32:02 [3680][1][FATAL] Array
(
)

03/28/18 11:32:13 [3680][1][FATAL] Array
(
)

03/28/18 11:32:32 [3680][1][FATAL] Array
(
[module] => Calls
[action] => index
[ajax_load] => 1
[loadLanguageJS] => 1
[return_action] =>
[return_module] =>
[Calls2_CALL_ORDER_BY] => date_start
[select_entire_list] => 0
[Calls2_CALL_offset] => 90
[show_plus] =>
[assigned_user_name] =>
[assigned_user_id] =>
[date_start] =>
[parent_type] => Accounts
[parent_id] =>
[parent_name] =>
[status] =>
[direction] =>
[searchFormTab] => advanced_search
[query] => true
[name_advanced] =>
[parent_type_advanced] =>
[parent_name_advanced] =>
[current_user_only_advanced] => 0
[status_advanced] => Array
(
[0] => Planned
)
[assigned_user_id_advanced] => Array
    (
        [0] => 1
    )

[showSSDIV] => yes
[saved_search_name] => 
[search_module] => 
[saved_search_action] => 
[displayColumns] => 
[hideTabs] => 
[orderBy] => DIRECTION
[sortOrder] => ASC
)

03/28/18 11:32:55 [3680][1][FATAL] Array
(
)

03/28/18 11:33:08 [3680][1][FATAL] Array
(
)

[/spoiler]

The repair function processes database tables and vardefs and then shows the recommendation to run the attached script. After doing so the system could be used but when starting the upgrade wizard to upgrade to the latest version a blank page appears with the message database: failure. Have tried the entire process several times with database repair before the update. No changes.

As I can’t find the error I refrain from doing the migration fearing to end in the dead end and won’t be able to do later upgrades.

Any idea how to overcome the problem?

pgr · 28 March 2018 14:50

Here are a bunch of loose ideas that you can investigate / try:

Check the compatibility Matrix to make sure you are respecting the requirements of the new SuiteCRM version:

https://docs.suitecrm.com/admin/compatibility-matrix/

Then try increasing in php.ini your memory_limit and max_execution_time and retry the upgrade.

Those log messages don’t make much sense to me. Please pay attention to the timestamps to make sure you’re showing me what’s happening during the upgrade attempt, not at another time.

That Calls2 I see there, is that a custom module you made?

There is an upgradeWizard.log that might have details of what’s going wrong.

schnellbgl · 29 March 2018 07:09

Thanks for the fast answer.

The compatibility requirements are met: php 5.6.32, Apache 2.4.29, MySQL 5.6.25.

Memory_limits and max execution time are set to high values.

Tried the upgrade this morning again. Everything went fine until step 4 of the upgrade wizard: Commit upgrade. After a certain time the prozess stoped and Database failure was shown (see screen shot). In a further screen shot you can see the history of my installation (all the upgrade already performed)

I have furthermore attached the upgrade wizard log and the sugarcrm log. In the latter a database error 1146 with missing fields/tables is given. In an earlier attempt I utilized the script which is proposed when using the repair function but this hasen’t solved the problem.

pgr · 29 March 2018 09:56

I can’t tell much from your logs, sorry. I don’t know if those tables are supposed to be there at that point in the script - I guess so. Maybe some command failed before that.

If you have a big enough business to be worth getting professional consultancy from SalesAgility, that would be my advice. You can make sure we help you get the migration right, and clean up your old stuff so that your future with SuiteCRM starts off on the right foot.

If not, that’s ok, I can continue to try helping you here for free, but without access to your server it’s harder to do.

I don’t have many more ideas for troubleshooting, though… I know sometimes these problems are solved by clearing up left-overs from old upgrades (in the upload/patch directory. Maybe you can try that.

Also make sure you check your web server log (errors.log or php_errors.log), there could be valuable clues in there.

schnellbgl · 31 March 2018 14:50

Thank you for your answer. I fully understand your position. Nevertheless I would appreciate if you could have a last look at my problem.

Have made an new attempt.Upgradeended apruptly as before and again the SQLscript (I have already posted) was offered when I used the repair function. This time I downloaded the script and started it in MySQL Bench. Each MySQL statement in the script resulted in an error. In total 3 different error codes were shown (attached the result. The first error of each kind is marked with color). I assume that the script does not comply with my version of MySQL (5.6.25) or is there another reason?

I am not familiar with MySQL and therefore cannot judge what is going wrong.