Release Notes: IBM Aspera Console 3.3.2

Product Release: March 14, 2018
Release Notes Updated: March 16, 2018

This maintenance release of IBM Aspera Console for Windows and Linux provides an upgraded SAML gem to address a SAML vulnerability. These release notes list system requirements and image information.


  • SAML gem is now at version 1.7.0 to address a vulnerability.


Windows Server: Windows 2008 R2, 2012, 2016
Linux: Red Hat 6-7, CentOS 6-7, SUSE 11-12 
Aspera Common Components 1.2.23
Browsers: Internet Explorer 8-11, Firefox 27-58, Safari 6-11, Chrome 40-65 
IE Browser Compatibility mode is now supported.


Linux 64-bit (rpm): aspera-console-
md5: d2ce6afc5bdb8cfd24584d5599183de1
sha1: 741edd373f3701e13b8136c791ec45ba72a7614a
Windows: AsperaConsole-
md5: f9fee8c4c31eb7df0a0598b9a6e24fc9
sha1: 3855c192d588a75d32df0dcac265dd70f80f4b6d


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

AC-592 - Console Space Watcher service is unable to start when the service is not running but the pid file exists. (CIM-1060)

AC-561 - Console does not support the exclude files by timestamp (exclude_newer_than and exclude_older_than) options in transfers between Node API endpoints.

AC-549 - Console shows encrypted async transfers as not encrypted, due to issue found in Enterprise Server 3.7.3 and Enterprise Server 3.7.4

AC-583 - SSL error appears randomly when users browse nodes.

AC-494 - Console cannot display account information for Windows managed nodes if the username contains a space, returning the error "undefined method 'downcase' for nil:NilClass". (CIM-589)

AC-483 - When creating a Watchfolder on a local node that has only Node API credentials, adding a new folder fails with a timeout error.

AC-468 - When running a Report with Report on set to last week, the query is run for the correct time frame but the Report Period End displayed in the report title is incorrect. (CIM-498)

AC-442 - The "Node API" endpoint type is not supported for clusters or unmanaged nodes.

AC-415 - [Linux] When upgrading from Console 2.3.0, the installer for versions 3.1.1 and newer fails with the error, "Mysql::Error: Data too long for column..." (CIM-383) Workaround: After installing the latest version of Console and Aspera Common Components but before upgrading, update MySQL settings with the following steps:
  1. Start MySQL.
    $ /etc/init.d/aspera_mysqld start
  2. Log into the Console database as root.
    $ /opt/aspera/common/mysql/bin/mysql -uUSERNAME -pPASSWORD aspera_console
  3. Edit the users table to allow long text strings.
    # ALTER TABLE users MODIFY view_filter TEXT;
  4. Stop MySQL.
    $ /etc/init.d/aspera_mysqld stop
  5. Continue with your upgrade.
    $ asctl console:upgrade

AC-398 - The Console dashboard returns a 500 Internal Server Error if a transfer session becomes stuck. (CIM-335)

AC-378 - When using failover groups, custom transfer settings do not propagate to the failover node. (CIM-296)

AC-376 - The Console map does not display in the Microsoft Edge browser. Microsoft Edge is not yet supported. (CIM-266)

AC-375 - When a transfer session fails to initiate, an incomplete record might be created that displays in Console but cannot be deleted. Workaround: Manually delete the session from central-store.db. (CIM-253)

AC-180 - If a managed node is removed from Console, attempting to delete saved endpoints associated with it from Preferences returns a 500 Internal Server Error.

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.

#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. 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