Turn Marketing Data into Revenue Intelligence. SugarChimp seamlessly syncs your SugarCRM and Mailchimp data in both directions—no manual updates, no stale lists. This real-time connection arms your sales team with richer, more meaningful insights into customer behavior.
#3043 - Issues uninstalling SugarChimp
I'm trying to uninstall SugarChimp. I'm currently on Sugar 7.8.2.0 release. The uninstall appears to work correctly and I did not receive any error messages during the uninstall process. I should mention that when I did the uninstall I selected the option Do Not Remove Tables. After the uninstall finished I ran Quick Repair and Rebuild. This finished with no errors.
Here is my problem; the Sugar Contact module and the Sugar Lead module will not load and display any data on my screen. When I click on those module names nothing happens. My screen is blank. I tried refreshing my screen for the Lead and Contact module and that did not solve my problem.
So any suggestions on how to fix this?
Thanks
Joe
-
"Amazing product and amazing people. Thanks a lot for all the help at any question! :D"
Read More Reviews
8 years ago
You can close this case as I fixed my problem.
After uninstalling SugarChimp I was having a compatibility problem with a new product from SugarCRM’s code named Mach 1. This product is in beta stage and the product apparently makes changes to the Sugar Lead and Contact module when you install it in your Sugar instance. Here is what I did to solve my problem; I successfully reinstalled MailChimp, then I successfully uninstalled Mach 1, ran a test and I was able to access the Sugar Lead and Contact module, then I successfully uninstalled MailChimp and ran a test and I was able to access the Sugar Lead and Contact module. All appears to be working okay.
I hope this information is helpful to you and you may want to contact your Sugar tech support point person for addition information.
8 years ago
Hello Joe,
Glad you were able to get it uninstalled successfully. It will be good for our records to know what was needed to fix the issue as these forums are public. Inevitably someone will run into this issue further.
Thanks again, Jon