Release Notes: Aspera Drive 1.3.5
Release Notes: Aspera Drive 1.3.5

Release Notes: Aspera Drive 1.3.5

Product Release: August 3, 2016
Release Notes Updated: August 3, 2016

WHAT'S NEW

Welcome to this release of IBM Aspera Drive. Drive 1.3.5 is a maintenance release that includes ascp version 3.6.2 and adds support for system proxy on Mac OS X.

ISSUES FIXED IN THIS RELEASE

ASDR-568 - Drive now initiates a sync action immediately after a conflict has been resolved between the local and remote repositories.

ASDR-567 - In Drive's Activity window, the right-click > Rescan now option has been moved. To initiate a rescan, do one of the following:
  • In the Activity window, Sync tab, right-click the account and select Sync settings.
  • In the Preferences window, Account tab, select the sync-configured account and click Settings.
Then, in the Sync Settings dialog, select Reset Sync and click OK.

ASDR-336 - Drive now successfully transfers Faspex 4.0.1 packages when the Faspex server is configured to use Azure storage.

#35545 - If your Faspex implementation is configured with SAML accounts but does not have a default set, Drive now offers autocomplete options for the workgroup name when you send files.

#35309 - Drive now supports the use of multiple identity providers (IdPs) for SAML authentication on your Faspex 4.x transfer server.

SYSTEM REQUIREMENTS

Windows

On your Aspera Drive client:

  • Windows 7 with Service Pack 1; Windows 8; or Windows 10

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, 10.10, or 10.11.

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

Mac OS X: AsperaDrive-1.3.5.129062.dmg
md5: def1828c92f30e5495b2f2a8a6d959fa
sha1: aa9475610ea2f544119cf370a11605c98a50f9b0
Windows: AsperaDrive-1.3.5.129062.msi
md5: 4356341850dbac7f2f60a1d1db51b2c7
sha1: 576e522919740a6aaaff9d82f093c6ae78a86455

KNOWN ISSUES

  • ASDR-607 - [Mac OS X only] Manual proxy with SAML accounts is not supported.
  • ASDR-599 - [Windows only] When Drive is configured to use HTTP proxy, if you make a transfer that includes a large number of attachments, Drive's status bar does not display the correct status. The status bar indicates that the transfer is complete, while in fact it is still in progress.
  • ASDR-342 - When you change the permissions for a SAML user in Shares, those new permissions settings are not reflected in Drive. To have the new permissions settings take effect, you must re-authenticate the user by re-adding that account to Drive.
  • ASDR-340 - [Windows only] With the PingFederate SSO provider, when you are logging into Drive, enter your login credentials and then press the Enter keyboard key (rather than using the Sign In button).
  • ASDR-188 - If you are using Drive with Aspera Faspex 4.0.0 and your Faspex implementation is configured with SAML accounts but does not have a default set, you must restart Drive in order to add any additional SAML accounts from the same Faspex server.
  • #36108 - [Mac OS X only] When Drive is manually configured to use an HTTP proxy, you cannot add a SAML Shares account. Workaround: Configure a system HTTP proxy, then configure Drive to automatically use the system proxy settings. You can do this in Drive's Preferences dialog > Network tab.
  • #34847 - If your transfer server's disk space is full, Drive may not offer the correct reason for the failed sync operations.
  • #34826 - [Mac OS X only] If you add a SAML account through a SAML server that uses an invalid certificate, Drive erroneously does not issue a warning.
  • #34722 - If a SAML account becomes invalid, Drive does not provide a way to re-enter the account credentials. To work around this issue, you must remove the account and then add it again.
  • #33660 - Drive incorrectly offers options for SAML authentication, even if SAML has not been configured for your Shares transfer server. In order for Drive to recognize whether your Shares server supports SAML, you must have Shares 1.9.3 or higher.
  • #33457 - When you attempt to create a Drive account for a SAML user whose account in Faspex or Shares has been disabled, Drive does not issue an error or notification.
  • #33384 - [Windows only] On Windows 10, Drive's shortcuts do not appear in the Quick access list in Windows Explorer.
  • #31919 - [Windows only] On Windows 8, if Drive accounts are created by the built-in Administrator user, the Aspera Drive option does not appear when you right-click files or folders in Windows Explorer. Workaround: When installing Drive, either install as a different user, or do a system-wide installation for all users.
  • #31869 - Node-to-node transfers are not supported. If you attempt a transfer from one node to another, the transfer fails and an error is recorded in the Drive Activity window.
  • #28181 - [Mac OS X only] Some configurations experience issues in syncing files with S3 storage.
  • #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.
  • #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.
  • #27153 - If the host is unreachable while Aspera Drive is sending a Faspex package, Drive may become unresponsive for approximately one minute.
  • #26725 - [Mac OS X only] An initial sync of a large number of files results in high CPU usage.
  • #26641 - Drive may encounter problems when it attempts to transfer files that have the same name but different case (for example, aspera1 and Aspera1).
  • #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.
  • #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.
  • #23230 - Aspera Drive cannot send packages to some valid Faspex usernames if those usernames contain the following special characters:

    < > ; ( ) &

  • #22789 - When a directory is renamed, then renamed again to its original name, the correct name may not appear in all Explorer windows.
  • #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.

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.