Created: December 23, 2009
Updated: May 10, 2010
- The new Connect Server Auto-Install feature. This is a Java-based applet installer for faster installations of Connect based on compatible browser and OS combinations.
- Connect Server layout has been updated.
- A new password confirmation dialog for Content Protected transfers has been added into Aspera User Interface.
- Change asperasync to honor the resume suffix in aspera.conf, so that files with the resume suffix are not transferred.
- A number of bug fixes.
This list covers the critical and major problems fixed in Enterprise Server 2.5.2.
- Aspera User Interface
- Fix issue with cannot chdir into a local directory that has UTF-8 characters on Windows 2008. (#3597)
- Fix asconfigurator to properly handle aspera.conf when the file size is greater than 256k (#5481)
- Fix transfers from starting immediately after a hot folder finished transferring (#5088)
- Fix installation destination of logger.pm into /var/aspera. (#5495)
- When the SSH Server feature is not installed during the Windows installation, the function to create new SSH keys is disabled. The error that you will see is the following: "Error generating OpenSSH keys:-1073741515" (#5718) Workaround: Use a 3rd-party SSH key generator application to generate key pair and copy into the user's /.ssh directory. Patch: Click here to dowload the patch for the Client release.
- Connect Auto-Installation
- On Windows, a non-administrator will not be able to uninstall Connect if it was installed via the applet installer and another user installed Connect via the applet installer and Connect is running. (#5600) Workaround: Notify the other user to close all browsers and Connect processes before running uninstallation.
- On Mac OS, during a Connect upgrade via the applet installer, the installation location is changed to ~/Library/Application Support/Aspera/Aspera Connect. (#5652)
- On Mac OS, if Connect 2.3.0 was installed by an administrator account, a non-administrator will not be able to upgrade to 2.3.1. The upgrade does not report any error, but Connect 2.3.0 will still be installed. (#5662) Workaround: Notify the administrator user to upgrade to Connect 2.3.1.
- Click here for more information and to download the Client patch release.