Product Release: March 24, 2016
Release Notes Updated: March 24, 2016
This release of IBM Aspera Console for Windows and Linux is a general maintenance release and provides the fixes and other changes listed below.Other Changes
- Security: Updated to OpenSSL 1.0.1s.
ISSUES FIXED IN THIS RELEASE
#34817 - The TransferInitiator background process fails to start after upgrading Console with added managed nodes that were never connected to the Console database.
#34776 - MySQL mis-optimized file linking query in some conditions results in slowdown of file processing.
#34726 - Legacy nodes that use SSH keys for admin credentials and have SSH tunnels enabled fail after upgrading Console.
#34710 - Console takes a long time to send an email when using an email template listing more than 10 file paths with hot folder transfers and a large database.
#34679 - (Linux Only) Killed and restarted mongrels leave defunct Ruby processes on Linux.
#34657 - When configuring a repeating smart transfer, users cannot leave the Until field empty to indicate that the transfer lasts forever. Editing the smart transfer automatically sets the field to one week from the present date.
#34633 - Using the Shares API to add a remote user from Active Directory to Console returns a 500 error.
Windows: 2008r2, 2012
Linux 64-bit: RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.15
Browsers: Internet Explorer 8-11, Firefox 27-45, Safari 6-9, Google Chrome 32-48
PREVIOUS RELEASE NOTES
IBM Aspera Console 3.0.5 Release Notes
IBM Aspera Console 3.0.3 Release Notes
IBM Aspera Console 3.0.2 Release Notes
IBM Aspera Console 3.0.1 Release Notes
Aspera Console 2.5.1 Release Notes
Aspera Console 2.3.2 Release Notes
md5: 2d7c3fc277f03a969338621d44df8a14 sha1: 8e7a3f14efbcdf15e70b433a5ab66150217bd32d
md5: 26a140cbe07e7704ee11c562e76e5e4a sha1: e24d69dc6ad18f9331afacbd2a268dcee3f05d35
#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.
#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to log in. Workaround: Turn off "Extended Protection" in ADFS SAML IdP. After doing so, you may at first see ADFS SAML user login failures with an "Invalid SAML response" error and infinite redirects on login. After some time, however, the failures end.
#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.