#2553 - Can't install SugarChimp in some Sugar instances
Hello,
I have been trying to install SugarChimp in several Sugar instances and in some of them I just can't install it.
I have been able to install it in a Sugar 7.7.1 clean instance in my local machine, however I haven't been able to do so in another instance in my local machine (not clean).
The installation stops after 15-20 seconds or so at the 80% and the trace is the following:
Installing administration extension Installing Language Packs Rebuilding Language...en_us Installing layoutdefs extension Installing scheduledefs extension Installing vardefs extension Rebuilding ActionViewMap... Rebuilding ActionFileMap... Rebuilding ActionReMap... Rebuilding Administration... Rebuilding Dependencies... Rebuilding EntryPointRegistry... Rebuilding Extensions... Rebuilding FileAccessControlMap... Rebuilding Layoutdefs... Rebuilding GlobalLinks... Rebuilding LogicHooks... Rebuilding TinyMCE... Rebuilding Menus... Rebuilding Include... Rebuilding ScheduledTasks... Rebuilding ScheduledTasks... Rebuilding UserPage... Rebuilding Utils... Rebuilding Vardefs... Rebuilding JSGroupings... Rebuilding WirelessModuleRegistry... Rebuilding WirelessLayoutdefs... Rebuilding TableDictionary... Rebuilding metadata for clients... Rebuilding Console... Installing Images Installing Relationships Rebuilding Vardefs... Rebuilding Layoutdefs... Rebuilding TableDictionary...
In my sugarcrm.log the last messages are:
... Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: bad data in last response Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: there is not a past validation Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: bad data in last response Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: there is not a past validation Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: bad data in last response Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: there is not a past validation Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: bad data in last response Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: there is not a past validation Tue Oct 4 08:04:05 2016 [18151][1][FATAL] SugarChimpOutfittersLicense::get_current_plan: bad data in last response
This is strange because I do have been able to install it in a copy of this instance in other machine (which is not local and has got public access).
Any ideas?
Thank you for your help,
David.
8 years ago
Hello David,
Sorry for the trouble. We've tested installation on all installs 6.5 - 7.7, locally as well as Sugar hosted, so I know we can get it figured out. Typically it comes down to a permissions issue within Sugar that causes hang ups. The best reference for what is needed to let add-ons install within Sugar is here: Sugar Permissions: Shane Dowling.
Let me know if that helps to track down the issues. Thanks!
8 years ago
More times than not, recently we've seen modules get stuck at 80% due to an elasticsearch issue.
Can you check your SugarCRM log to see if there are any errors there? We've found that when a package stops installing at 80% there is usually an error with the Elasticsearch indexes.
Here's a SugarCRM support post about the issue: https://community.sugarcrm.com/thread/28425
And here's another customer of ours who had the same issue: https://www.sugaroutfitters.com/support/zendesk-sugarcrm/2417
Let us know what you find. Once you get that issue resolved you should be able to reinstall the module without issue.
8 years ago
Hi Chad,
As you said, this is an "ElasticSearch" issue. Performing a "Full System Index" does the trick. However, this is the first time it happens to me, so the problem is probably related wich the package itself.
Thank you!
8 years ago
Good to hear! I've seen this happen across multiple modules now on the more recent versions of Sugar. I'm thinking it might be a Sugar 7.7 issue but I haven't been able to confirm that yet.
8 years ago
Nice Catch, thanks Chad. I'll close this case out for now. Let us know if we can do anything else to help, David. Cheers!