Jitterbit errors
Common Jitterbit Harmony errors, grouped by component. Open one for the exact error text, its likely causes, the fix and the official documentation.
- Errors
- 37
- Components
- 29
- Verified
- 37
- Official docs
- docs.jitterbit.com
37 errors in 29 groups
Amazon Bedrock connector1
Client certificates on Linux private agents1
Cloud Datastore1
Coupa connector1
Database connector1
Database connector (JDBC)1
Database connector (Kerberos)1
Database connector (MySQL)1
Database connector (ODBC Excel driver)1
Database connector (PostgreSQL ODBC)1
Database connector (SQL Server JDBC)1
Database connector (SQL Server MS JDBC)1
Database connector (SQL Server)1
Database Insert, Update and Upsert activities1
Design Studio NetSuite connector2
- NetSuite TBA: INSUFFICIENT_PERMISSIONINSUFFICIENT_PERMISSION at runtime in the Jitterbit NetSuite connector means the role used to generate the token-based authentication tokens lacks permissions for the operations. In NetSuite, use a Full Access or Administrator role when generating the tokens, or add the required permissions to the current role.
- NetSuite: Error getting the data center URLThis Jitterbit NetSuite error means the endpoint uses a generic or data center-specific WSDL URL, which NetSuite no longer accepts. In NetSuite, go to Setup, Company, Company Information and open the Company URLs tab to find the account-specific domain.
Design Studio project download1
Design Studio project import1
Design Studio transformations1
Environments and agent groups1
Harmony runtime1
Harmony single sign-on1
Operation validation2
- HTTP target activities can only send responses to one target activityThis Jitterbit Studio validation error means an HTTP target activity that writes its response to a second target is reused in another operation with a different second target. Duplicate the HTTP target activity in the Target 1 position of one of the affected operations.
- Operation is emptyThis Jitterbit Studio validation error means the operation has no steps. Add at least one operation step to the operation.
Private agents5
- Agent is incapable to process this messageThis Jitterbit ProcessEngine.log message means the agent has no free capacity, because every worker thread is in use or a capability metric reached its threshold. Review ProcessEngine.log for repeated capability status changes.
- Agent Not Running or UnreachableThis Jitterbit Studio message means the private agent services are not running or the agent host cannot reach the Harmony cloud. If the services are not running, start them. If a start fails, check the agent logs.
- Failed to find file in the local file storeThis Jitterbit transformation error means deployment metadata for a file did not fully sync from Harmony to the agent, which is usually transient. Re-run the operation. On agent 11.38 and later the metadata is restored on the next environment sync.
- No suitable driver foundThis Jitterbit error means the JDBC driver the connection needs is not installed on the private agent. Register the driver in JdbcDrivers.conf and copy its .jar file to JITTERBIT_HOME/tomcat/drivers/lib/.
- This connector was not found on the Jitterbit AgentThis Jitterbit error means the connector version the project requires has not yet downloaded to the agent, which is often transient. In Studio, open the affected connection and click Test, which triggers the agent to download the latest connector.
Salesforce connection1
Scripts1
Transformation mapping import1
Transformations3
- Failed to convert XML file to JSONThis Jitterbit transformation error means XML embedded in JSON contains a CDATA section, which is not supported. In a Jitterbit script, use Replace to swap the special characters inside the CDATA section, including the CDATA delimiters, for their escaped equivalents.
- Mappings of a target loop node depend on more than one source loop nodeThis Jitterbit transformation error means a target loop node has field mappings that reference two or more different source loop nodes. Open the transformation and identify the target loop node named in the error.
- String value length exceeds the maximum allowedThis Jitterbit transformation error means a single JSON string value exceeded the agent JSON parser limit of 20 MB. On a private agent running version 12.5 or later, set MaxStringLength in the [JsonParser] section of jitterbit.conf, for example 50000000 for 50 MB.
Transformations with connector JSON schemas1
Windows private agent installer1
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries
The iPaaS Brief
Subscribe to The iPaaS Brief.
The iPaaS newsletter for the people who run integrations. From iPaaS Group.
Free. You finish on theipaasbrief.com and confirm by email.