Overview
This article catalogs the error messages the Syspro integration can produce, grouped by the part of the integration they come from. Each entry gives the message as it appears, what causes it, and what to do about it.
All errors appear under Dashboard / Integration Monitoring / Error Logs in iPaaS.com.
Some integration behaviors produce no error at all. Records excluded by a mapping filter — gift-card-only orders, deposit sub-orders, orders in a status the integration does not process, invoices whose sales order has not yet transferred — are skipped silently and never reach the error log. If an expected record is missing from either system and no error was raised, check the relevant collection's filter rather than looking for an error. The Syspro Integration Known Limitations article and the mapping collection articles cover those cases.
Supported Flows
Connection and Authentication
Manual Sync
Syspro Data Transfer
iPaaS.com Data Transfer
Customer Lookup Formula
Connection and Authentication
Login Failure
Error message: Failed attempting to login to the Syspro Api
The message includes the response returned by the Syspro API where one was supplied.
Description: The integration could not obtain an access token from the Syspro REST API. This is raised when the API is reachable but rejects the login attempt, or returns a status other than success.
Resolution: Confirm the Syspro REST API is running and healthy on the subscriber's server. Confirm the API Url subscription setting points at the correct host. If the API is reachable and the failure persists, the API's own logs on the subscriber's server will show why the login was rejected — contact iPaaS.com Support at support@ipaas.com with that detail.
Connection Failure
Error message: (the underlying connection error, as reported by the network layer)
The text varies with the cause — a name that cannot be resolved, a refused connection, or a timeout.
Description: The integration could not reach the Syspro REST API at all. Nothing was returned to reject or accept.
Resolution: Confirm the Syspro REST API is running and that the host in API Url is correct and reachable from iPaaS.com. Enter the host name only — a value that already includes
https://produces an unusable address and every call fails. Confirm any firewall between iPaaS.com and the subscriber's network permits the traffic.
Manual Sync
Invalid Manual Sync ID — Whole Number Expected
Error message: Invalid key value at [location]. MappingCollectionType = [type], ExpectedDataType = Integer, PKValue = [value entered]
Description: A Manual Sync was started with an ID that is not a whole number, for a record type whose identifier must be numeric. The value entered appears at the end of the message.
Resolution: Re-run the Manual Sync using the correct identifier for that record type. Each mapping collection article documents the exact value its Manual Sync expects — for example the Syspro customer account number for a customer, or the Syspro stock code for a product.
Invalid Manual Sync ID — Two-Part Value Expected
Error message: Invalid key value at [location]. MappingCollectionType = [type], ExpectedDataType = String with one separator, PKValue = [value entered]
Description: A Manual Sync was started for a record type whose identifier is made of two parts joined by a separator, but the value supplied did not have that shape. Product inventory is the common case, because a stock position is identified by both the stock code and the warehouse.
Resolution: Re-run the Manual Sync supplying both parts of the identifier in the documented format. The relevant mapping collection article shows the expected shape and an example.
Invalid Manual Sync ID — Three-Part Value Expected
Error message: Invalid key value at [location]. MappingCollectionType = [type], ExpectedDataType = String with two separator, PKValue = [value entered]
Description: As above, for a record type whose identifier is made of three parts.
Resolution: Re-run the Manual Sync supplying all three parts in the documented format.
Invalid Record Identifier
Error message: Invalid data passed to [record type].SetPrimaryKey: [value]
Description: The identifier supplied for a record could not be interpreted as a valid key for that record type. This most often follows a Manual Sync started with a value belonging to a different record type.
Resolution: Confirm the identifier matches the record type being synced, and re-run. If the value is correct for that record type and the error persists, contact iPaaS.com Support at support@ipaas.com.
Syspro Data Transfer
Syspro API Call Failed
Error message: (the message returned by the Syspro API, followed by additional detail where the API supplied it)
Description: A call to the Syspro REST API failed. The message is the one Syspro returned, so its wording depends on what Syspro rejected — a missing required field, a value that does not exist in the subscriber's Syspro configuration, or a record that could not be created.
Resolution: Read the returned message: it names what Syspro objected to. Common causes are documented in the mapping collection articles — a stock code that does not exist in Syspro, an order type or tax code that is not configured in the subscriber's environment, or a customer record missing a name or email address. Correct the data or the Syspro configuration and re-run the transfer. If the message does not indicate a subscriber-correctable cause, contact iPaaS.com Support at support@ipaas.com.
Syspro API Returned an Unsuccessful Status
Error message: (the error detail returned with the unsuccessful response)
Description: The Syspro REST API responded, but with a status indicating the request was not carried out.
Resolution: As above — the returned detail identifies the cause. Confirm the record satisfies Syspro's own requirements for that entity before re-running.
iPaaS.com Data Transfer
iPaaS.com API Call Failed
Error message: (the message returned by the iPaaS.com API)
Description: A call to write a record into iPaaS.com failed. The message names the field or condition iPaaS.com rejected.
Resolution: The most frequent causes are a required field with no value — a product with no selling price, a customer with no email address, an inventory row whose warehouse has no matching iPaaS.com Location, or a tracking record whose shipping method does not match a configured Shipping Method. Each is documented in the relevant mapping collection article along with what to configure. Correct the cause and re-run the transfer.
Customer Lookup Formula
Customer Lookup Could Not Reach Syspro
Error message: Unable to retrieve Syspro Connection
Description: A mapping formula that looks up a Syspro customer by email address could not establish a connection to Syspro. The lookup cannot proceed, so the mapping produces no value.
Resolution: This follows the same causes as a connection failure — confirm the Syspro REST API is running and that API Url is correct. Once the connection is restored, re-run the transfer. If the connection is otherwise healthy and only this formula fails, contact iPaaS.com Support at support@ipaas.com.