Console 1.5.3/1.5.4 Release Notes

Console 1.5.3/1.5.4 Release Notes
Version 1.5.3 for Linux and 1.5.4 for Windows
Platform: Windows, Linux
Created: March 18, 2011
Updated: March 22, 2011

What’s New #1

  • New security and search performance improvements
  • Support for Aspera Enterprise and Connect Server 2.7, and Point-to-Point 2.7
  • Improvements to ASCTL and the installer
  • Dashboard Map
  • Smart Transfers
  • Improved Reporting
  • Many added features, including:
  • Third-party component upgrades
  • Significant bug fixes, as described in the “Fixed Issues” section below
  • Lines for transfer activity now include transfers where one side is an unmanaged node.
  • Option to allow users to share smart transfers that use personal saved logins
  • Creation of custom reports
  • Report scheduling and emailing
  • Custom Fields
  • Background Process Monitoring
  • Deleting Folders after Successful Transfers
  • SSH Tunnels
  • Backup and Purge
  • Upgraded to MySQL 5.1.54
  • Upgraded Apache 2.2.17
  • Upgraded Ruby 1.8.7


Fixed Issues

This list covers the critical and major problems fixed in this release.

  • Fixed Window installer issue where mySQL root password is overwritten by new installation (#5011). #1
  • Updated ETA computation so that it gets set to NULL if the transfer is predicted to last longer than ~360 days (#5239). #1
  • If a user attempts to add an invalid group name, they are no longer redirected to the Configuration page and instead are provided with an error message (#5409). #1
  • Fixed error that occurs after specifying wrong mySQL password during installation (when faspex is currently installed on the system) (#5489). #1
  • Fixed issue with bracketed transfer name not being shown on Activity and Node Details pages (#5498). #1
  • Fixed issue where “History” filter shows incorrect value if redirected to from Dashboard (#5711).
  • Updated unclear error messages and labels (#6299, #5854, #5849). #1
  • Fixed issue where transfer names (started from SCP GUI) containing certain Unicode character don’t appear in Console (#6311). #1
  • Fixed error that occurs when email template body is blank (#5655). #1
  • Fixed issues with email attachments (#6552, #6644) #1
  • Fixed error in Email Settings, where upon initial installation or upgrade, neither “Open Authentication” nor “Login Required” is selected (#4998). #1
  • Fixed issue where the reports page displays an HTTP 500 error when the report was generated from a deleted Advanced report template with a custom variable. (#9222)
  • Fixed IE8 problem where outline borders are missing from the boxes in the Smart Transfer diagram. (#9249)
  • Improved load time of the Smart Transfer page when a non-admin user with many Smart Transfers attempts to load the list. (#9250)
  • Fixed Smart Transfer problem where non-admin users were unable to create shared smart transfers using existing personal logins. (#9251)
  • Fixed Smart Transfer problem where a user was able to create a transfer with source=”node login” and dest=”personal login,” even though the user didn’t have explicit transfer path permission of ‘login’->’any’. (#9252)
  • Fixed problem where temp_bitrate was recalculated incorrectly even when users/bytes_transferred remained unchanged. (#9254)
  • Fixed HTTP 500 error on the Manage Reports page when the owner of the report is deleted from Console. (#9255)
  • Fixed basic report failure that occurred when viewing a scheduled report that a deleted user had created. (#9267)
  • Fixed problem where emails are not being sent. (#9320)
  • Fixed improper handling of special characters in the Custom Field value field. (#9334)
  • Fixed issue where the Excel (XLS) based report sent out as an email attachment does not display properly.  (#9336) #2 

Known Issues

  • Aspera Console 1.5 cannot run on the same machine as any version of Aspera Faspex.
  • Unable to delete the docroot settings from a Enterprise Server 2.5 node.  Workaround:  Upgrade Enterprise Server to 2.7. (#6006)
  • Apache startup on Windows logs the following harmless warning message:

            The Apache service named reported the following error:

>>> [Wed Jan 05 04:14:50 2011][warn](OS 2)The system cannot find the file specified. : No installed

ConfigArgs for the service "Apache HTTPD Server (Aspera)", using Apache defaults. (#8006)

  • When upgrading from Console 1.5.1 to 1.5.2, it is not necessary to run pre_upgrade.rb.  On Linux, the script will give an error.  On Windows, the script will run, but not do anything. (#9115)
  • On the “Connect” tab, changing the port from 40001 fails.  If the port is changed, Aspera Central will fail to reload.  The following error is thrown: “Network Error: Unable to contact Aspera Central server: Unable to connect to remote server/proxy. Connect attempted to, port <port #>.”  Restore the port to 40001 if you encounter this error. (#8635)
  • An advanced report that does not have a date range will fail to repeat at the scheduled time.  Workaround: Add $REPORT_PERIOD_END and $REPORT_PERIOD_START to the advanced report. (#8848)
  • Existing SSH Tunnels connections will fail if the "SSH Tunnel Start Port" is changed.  The connection status will report "SOAP Connection Problem."  Workaround: Connect a new node or Restarting the SOAP Poller will fix broken connections.  (#9153)
  • A scheduled report with a custom report period that is re-scheduled to repeat will run, but not repeat. (#9184)


Package Information

sha1sum value:

  • a77c23aeb12c70849bdb2ba1a1a6e3bd23b424b5  aspera-console-
  • b03ed5e3b202d6af5229db6f1b111517dd75e1c1  aspera-console-
  • 83dae731df78a6201d88859bc30c39b992557630  AsperaConsole-

MD5sum value:

  • 6e5e02eeb000cc26b9ac37b25b45f7cb  aspera-console-
  • 24f472bff2259a5a3a657653ade1d691  aspera-console-
  • 3964a67b8721655f95df3f2a24ccedb7  AsperaConsole-



#1 These features and fixes were originally introduced in Console 1.5.2.
#2 Fixed in Console 1.5.4 for Windows.

Powered by Zendesk