IBM Aspera Console 3.1.3 Release Notes
IBM Aspera Console 3.1.3 Release Notes

IBM Aspera Console 3.1.3 Release Notes

Product Release:
Release Notes Updated: March 28, 2017

This release of IBM Aspera Console 3.1.3 provides the fix listed below. These release notes also list system requirements, including supported platforms, and known problems.


AC-458 - Too many log entries in the database ingest logs fill up the disk. This log file is located at:
  • Windows: C:\Program Files (x86)\Aspera\Management Console\log\aspera_background\database_ingest\output.txt
  • Linux: /opt/aspera/console/log/aspera_background/database_ingest/output.txt


Windows:  2008r2, 2012

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

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


Linux 64-bit (rpm): aspera-console-
md5: b56abf45fc8f4275e7f856f149615270
sha1: 51d408a6082e7ba3c3d4bdf26252788b2dfcf72b
Windows: AsperaConsole-
md5: df8faade217f1e11d2d7b92ebda7d73f
sha1: 3c44667a627c268b80198edbb3f50eca1007eb1c


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.