Aspera Drive 1.2.1 Release Notes
IBM Aspera Drive 1.2.1 Release Notes

IBM Aspera Drive 1.2.1 Release Notes

  • Product Release Date: Feb. 11, 2015
  • Release Notes Updated: Feb.11, 2015

WHAT'S NEW

Welcome to this release of IBM Aspera Drive. Drive 1.2.1 is a maintenance release.

KNOWN ISSUES

  • #20513 - When you use Drive with Faspex to send a package to a dropbox, the dropbox name will not appear in the autocomplete options. Instead, you must type the dropbox name manually.
  • #22789 - When a directory is renamed, then renamed again to its original name, the correct name may not appear in all Explorer windows.
  • #23230 - Aspera Drive cannot send packages to some valid Faspex usernames if those usernames contain the following special characters:

    < > ; ( ) &

  • #24193 - [Mac OS X only] When you right-click a file for the first time after Drive has been installed, the Send to Faspex option is not available. However, it is available on subsequent attempts.
  • #25913 - During a sync scheduled in Aspera Drive, even if files on the Shares server are changing (that is, are in the process of being downloaded), Aspera Drive nevertheless attempts to sync those files, resulting in file errors and conflicts.
  • #26641 - Drive may encounter problems when it attempts to transfer files that have the same name but different case (for example, aspera1 and Aspera1.
  • #26725 - [Mac OS X only] An initial sync of a large number of files results in high CPU usage.
  • #27153 - If the host is unreachable while Aspera Drive is sending a Faspex package, Drive may become unresponsive for approximately one minute.
  • #27277 - [Mac OS X only] This issue affects users who attempt to upgrade Drive versions lower than 1.2.0 using the "Check for updates" feature. When the user first attempts an automatic update, the update action fails with an error message:
    Failed to run update. Mount location not found:
    /tmp/AsperaDrive
    If the user attempts the automatic update a second time, the update succeeds.
  • #27587 - Temporary files that applications (such as Microsoft Office) create are excluded from sync transactions because they can cause conflicts. The affected files are those with names of the form ~$* or ~*.tmp.
  • #27961 - [Windows only] If you updated your Windows installation between August 12 and October 14, 2014 (Microsoft Security Update KB2918614), you cannot install Drive system-wide as a domain user. The system produces the error message The profile for the user is a temporary profile. To address this, you must either
    • Uninstall Microsoft Security Update KB2918614.

      or

    • Install update KB3000988.
  • #28181 - [Mac OS X only] Some configurations experience issues in syncing files with S3 storage.

SYSTEM REQUIREMENTS

Windows

On your Aspera Drive client:

  • Windows 7 or 8

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or higher with a Sync-enabled license.

Mac

On your Aspera Drive client:

  • OS X 10.8, 10.9, or 10.0.

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or later with a Sync-enabled license.

PACKAGE INFORMATION

Windows: AsperaDrive-1.2.1. 99486.msi:
md5: bfed46cdc48b91a323faf791e91b9c09
sha1: c7c14173692f4b3ce1980436198403025967ebed
Mac OS X: AsperaDrive-1.2.1. 99486.dmg:
md5: 4c18dd27e5f346b606fb05a673aa012a
sha1: 4e8832da3706694b4b823d3f0acddd94964eb1c8

PRODUCT SUPPORT

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.