Skip to end of metadata
Go to start of metadata

Introduction

This page documents known issues that have been identified with recent versions of Jitterbit Harmony. For known issues that have been identified with Jitterbit Harmony Cloud Studio, see Cloud Studio Known Issues.

Harmony Portal

This section identifies issues with the current version of the Harmony Portal and any cloud applications accessed through it, including API ManagerMarketplaceManagement Console, and Citizen Integrator.

  • Windows Private Agents: Unable to install 64-bit agent with Two-Factor Authentication (TFA)

    • Summary: Installing a 64-bit Windows Private Agent fails if TFA is active.

    • Additional Info: The installer displays an error dialog.

    • Workaround: Temporarily disable TFA and install the 64-bit Windows Private Agent. After installation, enable TFA.

  • New trial users may not be able to access Cloud Studio immediately after registering
    • Summary: When a new trial user logs in to the Harmony Portal for the first time immediately after registering with Jitterbit Harmony, they may see Design Studio displayed as an application card. When clicked, nothing happens.
    • Additional Info: This issue is limited to new trial users; new users registering to join an existing Jitterbit Harmony organization are unaffected.
    • Workaround: To avoid this issue, wait a few minutes after registering to log in. If you have already encountered this issue, log out of the Harmony Portal and log back in. The Cloud Studio application card should be displayed. Click the card to access Cloud Studio.

  • Azure OAuth dialog has incorrect placeholder text

    • Summary: Placeholder text in the OAuth Token URL is incorrect.

    • More Info: The placeholder text https://login.microsoftonline.com/yourDirectoryID/oauth2/v2.0/oauth2/v2.0/token is incorrect.

    • Workaround: Enter the token in the format https://login.microsoftonline.com/yourDirectoryID/oauth2/v2.0/token.

Agents

This section identifies issues with recently released versions of Cloud Agents and/or Private Agents

Multiple Versions of Cloud and Private Agents

These issues apply to all recent versions:

  • Base64Encode adds newline characters in a long result string

    • Summary: The Jitterbit function Base64Encode adds a newline character (\n) after every 64th character of the encoded result string.

    • Additional Info: Result strings that are 63 or fewer characters long are unaffected.

    • Workaround: Use the Replace function to remove the newline character.

  • Workday: Migrating Design Studio operations between environments fails
    • Summary: Migrating a Workday operation between environments may fail with a Cannot compare value: WedServiceCall error.
    • Workaround: Use Import Jitterpak or Export as a Jitterpak instead of the Migrate command.

  • Windows Private Agents: Unable to install 64-bit agent with Two-Factor Authentication (TFA)
    • Summary: Installing a 64-bit Windows Private Agent fails if TFA is active.
    • Additional Info: The installer displays an error dialog.
    • Workaround: Temporarily disable TFA and install the 64-bit Windows Private Agent. After installation, enable TFA.

  • ODBC connections don't handle extended characters correctly

    • Summary: When connecting to a database using an ODBC driver, some extended characters, such as an en dash, aren't handled properly by operations that upsert data.
    • Additional Info: Upsert operations may fail, or succeed with unintended consequences by affecting the wrong data. Note that Insert and Update operations are unaffected by this issue.
    • Workaround: Use a JDBC driver for the Database connection (see instructions for Design Studio or Cloud Studio).

  • SFTP directories sometimes aren't auto-created
    • Summary: When writing to SFTP as a target using Design Studio or Cloud Studio, the auto-creation of directories works inconsistently.
    • Additional Info: Depending on the particular FTP server involved, the directory may not be created.
    • Workaround: Confirm that the directory has been created before production use.

  • SetSalesforceSession function doesn't work
    • Summary: The Jitterbit Script function SetSalesforceSession doesn't work correctly and shouldn't be used in Design Studio or Cloud Studio.
    • Additional Info: If used, the script may or may not generate an error. Even if the script does not generate an error, the function will not work correctly. As the function doesn't work, the built-in session handling of the Salesforce connector will be used.

  • Private Agents have specific system requirements and known issues
    • Summary: The Private Agents have different and specific system requirements and known issues, depending on the operating system being used.
    • Workaround: See the System Requirements for Private Agents for details.
  • 64-bit Windows Private Agent does not work with Windows Server 2008 R2 SP1
    • Summary: As of the 10.9 Harmony Releasethe 64-bit Windows Private Agent does not work on Windows Server 2008 R2 SP1.
    • Workaround: Install the 32-bit Windows Private Agent instead.
  • Agent installation fails due to PostgreSQL password including a plus sign (+)
    • Summary: Private Agent installation fails if the PostgreSQL password contains a plus sign (+). There is no error message displayed.
    • Additional Info: This is an issue with the Private Agent installer, not with PostgreSQL.
    • Workaround: Use a password without a plus sign (+). When installation is complete, the password can be changed to any password acceptable for use with PostgreSQL.

10.38 Linux Private Agents

  • The PostgreSQL database is reinitialized when upgrading from version 10.37 to 10.38
    • Background: When upgrading a Linux Private Agent from a pre-10.37 version to a version that is 10.37 or later, the PostgreSQL database will be reinitialized as it is upgraded to version 9.6. This upgrade will recreate the database on your Private Agent and your data will be recovered during this upgrade process. After the upgrade, any backups created using an earlier PostgreSQL version will not be compatible. The upgrade process can take more than 30 minutes depending on the number of projects and the size of the environments associated with your Private Agent group. Any pending jobs will be put in a pending queue to be run after the upgrade is complete. This upgrade does not involve the Windows Private Agent.
    • Known Issue: It is a known issue that when upgrading a Linux Private Agent from version 10.37 to 10.38, the PostgreSQL database is reinitialized.
    • Workaround: Upgrade to a Linux Private Agent that is version 10.39 or later.

10.0 Cloud and Private Agents

  • The Cloud Studio Cherwell connector doesn't work
    • Summary: As of the 10.1 Harmony Release, a change made to the Cherwell connector in Cloud Studio means it is no longer compatible with 10.0 agents.
    • Workaround: If using the Cherwell connector, please upgrade to 10.1 agents or higher.

9.8 Private Agents

  • Plugins aren't executing
    • Summary: An issue with plugins failing to run resulted in the Private Agent download being pulled shortly after the release.
    • Workaround: If you still have a 9.8 Private Agent, please upgrade to a later version.

Design Studio

This section identifies issues with recently released versions of Design Studio.

Multiple Versions of Design Studio

These issues apply to all recent versions:

  • Autodesk Fusion Lifecycle: Authentication API V3 is not supported
    • Summary: As of December 18, 2020, Autodesk no longer supports the versions (V1/V2) of the authentication APIs used in the Autodesk Fusion Lifecycle Connector. As a result, the connector may stop working.
    • Additional Info: Jitterbit is in the process of upgrading the connector to use authentication API V3.
    • Workaround: Until the connector supports V3, you must request an extension from Autodesk to continue using the connector. Autodesk is allowing extensions through March 31, 2021 to continue using V1/V2. For details on requesting an extension, see Action Required for Fusion Lifecycle Administrators Prior to December 18, 2020.

  • SOAP faults that trigger an email message can't be deployed
    • Summary: When attempting to deploy an operation containing a SOAP fault that triggers an email message, you may receive an error.
  • Microsoft Dynamics AX: Optional mappings with invalid values cause a CustomerServiceClient:create function to fail
    • Summary: After configuring a Microsoft Dynamics AX Function with its CustomerServiceClient:create function, if the request transformation contains any mappings to optional fields that provide an invalid value, the operation will fail at runtime. An example of an invalid value is providing U.S. dollars instead of a valid currency ISO code for the Currency field.
    • Additional Info: The operation fails with an error related to a failed login and no exceptions are logged in the Microsoft Dynamics AX system.

9.4.1 Design Studio

  • Environment can't be set and recipes can't be downloaded
    • Summary: This version has issues with setting the environment and downloading recipes.
    • Workaround: If you are still using version 9.4.1, please upgrade to a later version.

8.25 Design Studio

  • JavaScript: Global variables aren't working
    • Summary: Global variables aren't able to be assigned or referenced in a JavaScript.
    • Workaround: Use the Jitterbit Script language for any scripts containing global variables or upgrade to a later version.

8.5 and Earlier Design Studio

  • Deployment error using Design Studio 8.5 and earlier
    • Summary: As of the 10.40 Harmony release, projects can no longer be deployed using Design Studio versions 8.5 and earlier. These Design Studio versions are at end-of-life and are not supported.
    • Additional Info: When attempting to deploy, you may receive this error:

      org.jitterbit.integration.client.server.IntegrationServerException: java.lang.NullPointerException
    • Workaround: Upgrade to a supported Design Studio version.

SAP Event Listener

This section identifies issues with recently released versions of SAP Event Listener.

Multiple Versions of SAP Event Listener

These issues apply to all recent versions:

  • SAP Event Listener: The Windows configuration UI cannot be opened 
    • Summary: On attempting to open the Windows SAP Event Listener configuration through the UI, an exception occurs.
    • Additional Info: This issue occurs when a previously saved configuration that includes the required outer set of <events> and </events> tags in the Event Details field has since been inadvertently saved without those tags.
    • Recovery: Manually edit the configuration file at C:\ProgramData\JitterbitSAPEventListener\conf\sapeventconfig.xml to replace the required outer tags. The Windows configuration UI can again be opened.

Data Loader

This section identifies issues with recently released versions of Data Loader.

8.16.13.1 Data Loader - June 27, 2019

  • Erroneous warning during installation must be acknowledged
    • Summary: During installation of Data Loader 8.16.13.1 (using the updated installer available as of June 27, 2019) on macOS 10.14 (Mojave), you will receive a warning that "'JitterbitInstallConfigUtils' is not optimized for your Mac and needs to be updated."
    • Workaround: Acknowledge the warning. The installation should proceed successfully.

8.13 - 8.16.13.1 Data Loader - December 20, 2016

  • Installer is not compatible with macOS 10.14 (Mojave)
    • Summary: Those using macOS 10.14 (Mojave) cannot install Data Loader 8.16.13.1 (using the original installer released December 20, 2016) due to an issue with compatibility of the installer.
    • Workaround: Install Data Loader using the 8.16.13.1 installer available as of June 27, 2019 on the Downloads page of the Harmony Portal.