IBM Aspera Console 3.1.1 Release Notes

Product Release: November 1, 2016

Release Notes Updated: November 1, 2016

This release of IBM Aspera Console 3.1.1 provides the new features, fixes, and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.


  • Configuration
  • Watch Folder
    • Admins can now configure the number of watch folders to display per page when browsing configured watch folders in Console (Configuration > Defaults > Watchfolders per page).
    • Console now supports retrying failed drops in watchfolder transfers. View the details of failed drop and click the Retry drop link. Console sends a retry request to the watch folder server, which creates a new drop.
  • System
    • OpenSSL has been upgraded to version 1.0.1u.


AC-151 - Node Info collector for Console periodically reports a NodeApiUnreachableError.

AC-149 - Users cannot disable content protection for Smart Transfers.

AC-133 - Upgrading a node from ES 3.6.2 to 3.7.1 may remove the Archive Directory path for the Source Archiving feature.

AC-132 - Upgrading a node from ES 3.6.2 to 3.7.1 clears the Source Archiving enabled checkbox.

AC-126 - The drop-down menu for searching by nodes in the advanced search should be sorted by name.

AC-125 - Deleting personal saved login for unmanaged node fails with 500 error.

AC-118 - Clicking on an Unmanaged Node to navigate to the Node details page fails with 500 error.

AC-105 - Transfers report a "DB never reported session end" error.

AC-104 - Console should sort file list by id DESC instead of file_index DESC.


Windows:  2008r2, 2012

Linux 64-bit:  RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.18

Browsers:  Internet Explorer 8-11, Firefox 27-45, Safari 6-9, Google Chrome 32-48


Aspera Common Components: aspera-common-
md5: 663712e833886d0f1deafd617982f66e
sha1: 50c583cd8677ca6f8af8438d940dc6ca4d7ede9c
Linux 64-bit (rpm): aspera-console-
md5: 6c5ca32c8b1c1241a88cd049042f9241
sha1: 945e215b638b94b216df1a508bb84a792e789bc0
Windows: AsperaConsole-
md5: 56c3a2687c2ffa21fba2ed1e24433d1a
sha1: d2fc1f2f89d5a71a7184ff88483fc6c60ee37245


Note: This release contains tickets created from different tracking systems. For this reason, the ticket IDs may reflect different numbering formats.

AC-117 - After restarting Watchfolder services, the details page in Console does not display previously transferred files. This is issue will be fixed in an upcoming release of Enterprise Server.

NODE-137 - The Node API reports an incorrect count of failed files.

NODE-133 - The Node API reports the incorrect completion time for a transfer.

NODE-123 - If a transfer is canceled or it errors out, and it is retried before Console has a chance to poll the node, Console fails to mark the file as errored and instead adds a new file record when resuming the transfer. Both the original and new record appear in the Session Files table on the Session Details page, but the original record remains a normal, green bar and is never updated.

ES-53 - Cluster to cluster transfers are not supported.

#31098 - (Linux Only) Upgrading the common components from version 1.2.9 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Console or Orchestrator after upgrading the common components will recreate the missing link during the installation process.

#27236 - Console generates reports of the type XLSX (rather than XLS). Any reports completed before upgrading from a version of Console prior to 2.5 are no longer accessible through the web link. However, any reports that were not completed before the upgrade (such as scheduled reports) are unaffected: a report configured to generate XLS generates XLSX when it next runs. Workaround: Click Rerun on a completed report.

#22396 - If upgrading from a version of Console prior to 2.0.1, email notifications are configured for specific transfer paths on a user’s Preferences > Email Notifications page, these settings are not honored when the user clicks the Rerun link on the Activity page on a transfer that started before the upgraded.

#22303 - If upgrading from a version of Console prior to 2.0.1, scheduled smart transfers that were created before upgrading continue to use the old behavior, displaying dates/times using the timezone of the transfer requester, rather than trying to look up the recipient's time zone.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.

Powered by Zendesk