by Rolustech

Boost your SugarCRM with seamless Google integration. Sync contacts, meetings, and Drive files. Streamline workflows and elevate productivity.

Free Trial

By clicking you consent to share your profile with the developer

#390 - Error: redirect_uri_mismatch

Closed Installation created by IntelaCloud 10 years ago

Getting this error, where <my domain> is a masquerade to protect our identity:

The redirect URI in the request: http://<my domain>/CRM/index.php?module=Users&action=GoogleOauth did not match a registered redirect URI Learn more Request Details cookie_policy_enforce=false scope=http://www.googleapis.com/auth/drive response_type=code redirect_uri=http://<my domain>/CRM/index.php?module=Users&action=GoogleOauth access_type=offline display=page user_id=admin@<my domain>.com hd=<my domain> prompt=consent client_id=121212121212

What do I need to do with Google Apps to make this work? Thanks.

  1. jason member avatar

    jason Verified Purchase

    10 years ago

    Hello,

    I've move the support case over to Gmail and Google Sync. Rolustech should be able to help you further. From looking at past cases here, it looks like your URI needs to be added to their console for the Document sync to work. This is where the error is coming from. The calendar, email, and contact sync should work in the meantime. For now, it may be best to disable the document sync until that step is completed by Rolustech.

    You should hear something shortly when the URI has been added.

    Thanks! -Jason

  2. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    We have added intelcloud uri . Please check now and let us know

    Thanks,

  3. admin3 member avatar

    IntelaCloud

    10 years ago

    Excellent. I had to add the extra lines to config_override.php to deal with cross site attack checks, and all seems to have gone through with Google. Now, at what point should I expect to start seeing data from my Google Apps account (contacts, calendar items, Drive documents, etc.)? Right now I see nothing. Thanks.

  4. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    Make sure that schedulers are active and running. Create/update any calendar item/contact or drive file in Google and wait for scheduler to run, these items will be synced automatically to SugarCRM if you have enabled it in GSync settings.[from Google to sugar check-box is checked]. You can get detail about all available options/choices from user guide provided in documentation section on this website But if you have any contact/calendar item/document then all these should be synced after successful installation.

    Thanks,

    • admin3 member avatar

      IntelaCloud

      10 years ago

      I've double and triple checked things. Cronjobs are running and logs recorded in the Scheduler. Not seeing any errors in /var/log/cron nor messsages. The only data I'm seeing from Google are documents (Drive). No contacts and no calendar items. What have I missed? Thanks.

  5. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    If drive is working means sync process is running but there might be any issue with contacts and calendar. Send us your sugarcrm log file not server log file or cron log file. sugarcrm.log file can be found at root directory of your SugarCRM installation. For example if you have installed it on /var/www/crm/ then you can find sugarcrm.log file in crm directory.

    Thanks, Support

  6. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    Unfortunately this support channel does not allow attachments so you can communicate us via support@rolustech.com

    Thanks, Support

  7. admin3 member avatar

    IntelaCloud

    10 years ago

    Below is the last 40 of the log. Not really informative. Even successful document syncs show as FATAL.

    Wed Feb 5 10:34:02 2014 [19718][1][FATAL] STARTED: Contacts sync: admin(admin@intelacloud.com) Wed Feb 5 10:34:02 2014 [19718][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:34:02 2014 [19718][1][FATAL] Job 9f54fa6e-a759-d784-7923-52f259ab423a (GSync- Contacts) failed in CRON run Wed Feb 5 10:35:02 2014 [19759][1][FATAL] STARTED: Calendar sync: admin(admin@intelacloud.com) Wed Feb 5 10:35:02 2014 [19759][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:35:03 2014 [19759][1][FATAL] Job 1eff7813-82da-c5a7-ba44-52f259433788 (GSync- Calendar) failed in CRON run Wed Feb 5 10:36:02 2014 [19850][1][FATAL] STARTED: Contacts sync: admin(admin@intelacloud.com) Wed Feb 5 10:36:02 2014 [19850][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:36:02 2014 [19850][1][FATAL] Job 521d666c-e7fb-1b2e-ac30-52f25a6f8f72 (GSync- Contacts) failed in CRON run Wed Feb 5 10:37:02 2014 [19891][1][FATAL] STARTED: Drive sync: miker(mike.rathburn@intelacloud.com) Wed Feb 5 10:37:02 2014 [19891][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:37:04 2014 [19891][1][FATAL] SUGAR-TO-GOOGLE Wed Feb 5 10:37:04 2014 [19891][1][FATAL] COMPLETED: Drive sync: miker(mike.rathburn@intelacloud.com) Wed Feb 5 10:37:04 2014 [19891][1][FATAL] STARTED: Calendar sync: admin(admin@intelacloud.com) Wed Feb 5 10:37:04 2014 [19891][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:37:05 2014 [19891][1][FATAL] Job bdef8cbf-db35-5311-543d-52f25a326b0f (GSync- Calendar) failed in CRON run Wed Feb 5 10:38:02 2014 [19945][1][FATAL] STARTED: Contacts sync: admin(admin@intelacloud.com) Wed Feb 5 10:38:02 2014 [19945][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:38:02 2014 [19945][1][FATAL] Job ea20f8f4-53a8-498a-da55-52f25abe7dcc (GSync- Contacts) failed in CRON run Wed Feb 5 10:39:02 2014 [19986][1][FATAL] STARTED: Calendar sync: admin(admin@intelacloud.com) Wed Feb 5 10:39:02 2014 [19986][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:39:02 2014 [19986][1][FATAL] Job c0fe727e-3d0c-5ec3-3218-52f25af156de (GSync- Calendar) failed in CRON run Wed Feb 5 10:40:02 2014 [20040][1][FATAL] STARTED: Contacts sync: admin(admin@intelacloud.com) Wed Feb 5 10:40:03 2014 [20040][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:40:03 2014 [20040][1][FATAL] Job eea8e8c5-ab74-33e1-76ba-52f25b3314ae (GSync- Contacts) failed in CRON run Wed Feb 5 10:41:02 2014 [20145][1][FATAL] STARTED: Calendar sync: admin(admin@intelacloud.com) Wed Feb 5 10:41:02 2014 [20145][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:41:02 2014 [20145][1][FATAL] Job 68529ca0-c298-1dc1-5e55-52f25b8af14c (GSync- Calendar) failed in CRON run Wed Feb 5 10:42:02 2014 [20199][1][FATAL] STARTED: Drive sync: miker(mike.rathburn@intelacloud.com) Wed Feb 5 10:42:02 2014 [20199][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:42:07 2014 [20199][1][FATAL] File downloaded successfully location: upload/2c4f6310-33a9-ecb6-a894-52f25b1e88d2 Wed Feb 5 10:42:07 2014 [20199][1][FATAL] Document: IntelaCloud.txt with id 3ca2fc28-e814-7919-81c9-52f19c6fcefb saved in SugarCRM. Wed Feb 5 10:42:07 2014 [20199][1][FATAL] SUGAR-TO-GOOGLE Wed Feb 5 10:42:07 2014 [20199][1][FATAL] COMPLETED: Drive sync: miker(mike.rathburn@intelacloud.com) Wed Feb 5 10:42:08 2014 [20199][1][FATAL] STARTED: Contacts sync: admin(admin@intelacloud.com) Wed Feb 5 10:42:08 2014 [20199][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:42:08 2014 [20199][1][FATAL] Job cc06523f-1060-727e-f579-52f25b969a1d (GSync- Contacts) failed in CRON run Wed Feb 5 10:43:02 2014 [20240][1][FATAL] STARTED: Calendar sync: admin(admin@intelacloud.com) Wed Feb 5 10:43:02 2014 [20240][1][FATAL] GOOGLE-TO-SUGAR Wed Feb 5 10:43:03 2014 [20240][1][FATAL] Job 48cfb26d-64e0-3ff6-d2c9-52f25b3273c8 (GSync- Calendar) failed in CRON run

  8. admin3 member avatar

    IntelaCloud

    10 years ago

    What's happening folks?

  9. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    this log is minimal and we can 't identify issue. we need following information about your sugarcrm instance. 1. SugarCRM version? 2. Onsite or Ondemand? 3. GSync(our plugin) version?

    Thanks, Support

  10. admin3 member avatar

    IntelaCloud

    10 years ago

    Last call folks before I back out of this plugin.

    • jason member avatar

      jason Verified Purchase

      10 years ago

      Hello Rolustech and IntelaCloud,

      Stepping through the code it looks like the errors that are being thrown in the log are likely to trace back to to some user's gmail ID and password being incorrect and/or the oAuth setup for Drive not being configured correctly. The "(GSync- Contacts) failed in CRON run" error gets thrown in include/SugarQueue/SugarCronJobs.php and the "GOOGLE-TO-SUGAR" in the previous log entry can be found in custom/include/Google/GoogleHelper.php. The only thing that I can spot after that point and before jobFailed() is called is around the user authentication point.

      Hopefully this helps pinpoint the cause.

      -Jason

    • admin3 member avatar

      IntelaCloud

      10 years ago

      The Google Drive items sync great on all accounts. Only the Contacts and Calendars do not.

    • jason member avatar

      jason Verified Purchase

      10 years ago

      Very odd. I don't expect you to do this, but if you want to try to locate the point of failure you could throw some logging inside of /custom/include/Google/ContactHelper.php->updateFromGoogle() to see if it gets there and where inside it fails.

      There seems to be a bit of difference between how the Drive sync/authentication works that with the Contacts/Calendar piece. This is just an observation as an outsider as I'm not familiar with what is under the hood. Just know that it has been working well for me.

      -Jason

  11. rolustech-primary-contact member avatar

    Rolustech Verified Purchase

    10 years ago

    Hi,

    Can you please, set log level as debug and after 20 minutes of setting this(20 minutes because jobs should be run twice ), get your sugarcrm log file and send to us. If you are unable to do this then no worry , we can help you by screen sharing session.

    Thanks, Support

  12. admin3 member avatar

    IntelaCloud

    10 years ago

    I cancelled the order, uninstalled the plugin and gave a thumbs down review for v6.5.16. You guys make it work and I'll revisit then. Thanks.

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
Rating