Release Notes: IBM Aspera Console 3.1.2
Release Notes: IBM Aspera Console 3.1.2

Release Notes: IBM Aspera Console 3.1.2

Product Release:
Release Notes Updated: February 24, 2017

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


  • Console now supports a rake task to upload a license to Console.
  • Console now supports migration of Console to use RDS.


AC-410 - Error in MySql config file breaks logging in legacy nodes.

AC-405 - Console now supports a rake task to change the local node's name.

AC-192 - Half of the Accounts/Users table is missing when using IE with Compatibility Mode enabled.

AC-179 - Restoring Console database from backup returns MySql error: "rake aborted".

AC-167 - From time to time, Console gives a 500 error when loading the Activity or Advanced Search pages after a transfer has been recently deleted.


Windows: 2008r2, 2012
Linux: RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.20
Browser: Safari 6-9, Firefox 27-45, or Chrome 32-48


Linux 64-bit (rpm): aspera-console-
md5: 7802197abf3ed542ae291fc522107919
sha1: 844d81520c8f1bf2e0015f38384bf338501f20db
Windows: AsperaConsole-
md5: 26fc507dd79d9361644e511b50b663e4
sha1: df6dc2d62f316fb5b84d412a323a177c0568aa10


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.