Skip to main content

SugarCRM Error Messages

Errors a subscriber may see for the SugarCRM integration in iPaaS.com, with what causes each one and how to resolve it.

Overview

This article catalogs the errors a subscriber may encounter with the SugarCRM integration. Errors appear under Dashboard / Integration Monitoring / Error Logs in iPaaS.com. The SugarCRM integration does not add its own validation rules to the mappings, so most errors originate in SugarCRM and are shown in the error log exactly as SugarCRM returns them, along with the HTTP status code.

Supported Flows

  • Connection and Authentication

  • Account and Contact Transfers

Connection and Authentication

Connection could not be established

Error message: An authentication or connection error returned by SugarCRM (for example, an "unauthorized" response), shown when iPaaS.com tries to connect.

  • Description: iPaaS.com could not obtain an access token from SugarCRM, or the validation request was rejected. This usually means the API URL, Username, or Password is incorrect, or the SugarCRM user does not have API access.

  • Resolution: Confirm the API URL is entered without a https:// prefix (for example, demo.sugarcrm.com/rest/v11_25), and that the Username and Password belong to a SugarCRM user with read/write access to Accounts and Contacts. Re-establish the connection from the subscription settings. See SugarCRM Connections and Settings.

Account and Contact Transfers

SugarCRM rejected the request

Error message: The error message returned by SugarCRM, together with an HTTP status code (for example, a 400 or 403 response).

  • Description: SugarCRM declined to create, update, or delete an Account or Contact. Common causes are a required SugarCRM field missing from the data, a value that fails a SugarCRM validation rule, a referenced record that no longer exists, or a permission the API user does not have.

  • Resolution: Open the error under Dashboard / Integration Monitoring / Error Logs and read the message SugarCRM returned. Correct the source data, or adjust the SugarCRM API user's permissions, then re-run the transfer. If the SugarCRM message is unclear, contact iPaaS.com Support at support@ipaas.com.

SugarCRM could not be reached

Error message: A connection error, such as a timeout or a host-not-found response, shown when the request cannot reach SugarCRM.

  • Description: iPaaS.com could not connect to the SugarCRM API. The SugarCRM instance may be offline or unreachable, or the API URL may be wrong.

  • Resolution: Confirm the SugarCRM instance is online and reachable and that the API URL on the subscription is correct, then re-run the transfer. If SugarCRM is reachable but the error continues, contact iPaaS.com Support at support@ipaas.com.

Related Documents

Did this answer your question?