Overview

This article catalogs every error the SugarCRM integration can record in the iPaaS.com error logs, which you will find under Dashboard / Integration Monitoring / Error Logs. Each entry gives the error's permanent code, the message as it appears in the log, what causes it, and how to resolve it. A code never changes once it is published, even if the wording of the message is improved later, so the fastest way to use this page is to copy the code out of the error log and search for it here.

SugarCRM codes have three segments, as in SUGR-AUTH-1001, where SUGR identifies the SugarCRM integration. A code with only two segments, such as VALD-1002, comes from the iPaaS.com platform rather than from this integration and is documented in the platform's own error reference.

Some resolutions below refer to your Managed Integration Service Provider (MiSP) — the partner who set up and maintains your integration. Your MiSP owns your mapping configuration, your connection credentials and settings, and any reconciliation between SugarCRM and iPaaS.com, so they are the right first stop whenever a resolution calls for a configuration change.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

Supported Flows

Connection and Authentication
Account and Contact Transfers

Error Collection

Connection and Authentication

Could not authenticate to SugarCRM

SUGR-AUTH-1001 - Could not authenticate to SugarCRM. Verify the API URL, Username, and Password in the subscription settings. {Details}

Description: iPaaS.com could not obtain an access token from SugarCRM when opening the connection, or could not refresh one that had expired. Nothing was transferred, because the failure happens before any account data is sent. {Details} carries the underlying reason. Most often it points at an incorrect API URL, Username, or Password on the subscription, or a SugarCRM user whose API access has been withdrawn or whose password has expired — but it can also report that SugarCRM's reply could not be read at all, which usually means the API URL is reaching something other than the SugarCRM API.
Resolution: Read {Details} first, because it distinguishes a credential problem from an address problem. For a credential problem, confirm the Username and Password belong to a SugarCRM user with API access and read/write permission on Accounts and Contacts, and sign in to SugarCRM directly with those credentials to check the password has not expired. For anything that suggests SugarCRM's reply could not be read, confirm the API URL is your SugarCRM host and REST path without a scheme prefix — for example demo.sugarcrm.com/rest/v11_25, not https://demo.sugarcrm.com/rest/v11_25. Re-save the settings to re-establish the connection. If the credentials and address are both correct and the connection still fails, ask your MiSP to confirm the subscription is pointed at the SugarCRM instance you intend to use. See SugarCRM Connections and Settings.

SugarCRM rejected the connection validation request

SUGR-AUTH-1002 - SugarCRM rejected the connection validation request. {Details}

Description: iPaaS.com obtained a token from SugarCRM, but the validation request that follows it — a read against the Accounts module — did not succeed. {Details} is SugarCRM's own response to that request, so its wording comes from SugarCRM rather than from iPaaS.com; where SugarCRM returns nothing at all, {Details} reads SugarCRM returned no detail. The most common cause is a SugarCRM API user who can authenticate but does not have permission to read Accounts; the instance being unavailable will also produce this error.
Resolution: Read the SugarCRM response carried in {Details}. If it reports a permissions problem, have your SugarCRM administrator grant the API user read access to the Accounts module, then re-save the subscription settings to revalidate the connection. If it reports that the instance is unavailable or under maintenance, revalidate once SugarCRM is back online. If the response instead points at the address or user being used, ask your MiSP to review the API URL and Username on the subscription.

Account and Contact Transfers

SugarCRM could not be reached

SUGR-EXTN-1001 - iPaaS.com could not reach SugarCRM while attempting {Action}. {Details}

Description: The request never arrived at SugarCRM. {Action} names the operation that was being attempted, such as CREATE Account (Acme Corp), and {Details} carries the underlying network error — commonly a host that could not be resolved, a refused connection, a certificate problem, or a timeout. Either the SugarCRM instance was unreachable at that moment, or the API URL points at a host that does not exist.
Resolution: Confirm the SugarCRM instance is online, then re-run the transfer; a one-off network failure normally clears on the next attempt. If it keeps failing, compare the API URL on the subscription against your SugarCRM instance's actual host name and ask your MiSP to correct it if they differ. If SugarCRM opens normally in a browser but the integration still cannot connect, ask your SugarCRM administrator to confirm the instance accepts API requests originating outside your own network.

SugarCRM rejected the request

SUGR-EXTN-1002 - SugarCRM rejected the {Action} request (HTTP {StatusCode} {StatusName}). {Details}

Description: SugarCRM received the request and refused it. {Action} names what was attempted, such as CREATE Account (Acme Corp) or DELETE Account (9f2c1b4e); {StatusCode} and {StatusName} are the HTTP status SugarCRM returned; and {Details} is SugarCRM's own response body. This entry covers every rejection SugarCRM sends back during an Account or Contact transfer, so the specific cause is always in {Details}. The usual causes are a required SugarCRM field that the mapping did not populate, a value that failed a SugarCRM validation rule, a referenced record that no longer exists, or an API user without permission for that module or operation.
Resolution: Read the {Details} portion of the message first — SugarCRM normally names the field or rule that failed. A 400 means the data sent did not satisfy SugarCRM: correct the source record, or ask your MiSP to adjust the mapping so the required field is populated. A 403 means the API user lacks permission for that module or operation, which your SugarCRM administrator can grant. A 404 means the Account or Contact being updated or deleted no longer exists in SugarCRM. Re-run the transfer once the underlying cause is corrected. If SugarCRM's response is not specific enough to act on, contact iPaaS.com Support at support@ipaas.com with the error code, the full message, and the time of the transfer.

SugarCRM Error Messages