Release Notes: Aspera Drive 2.1.1

Product Release: May 12, 2017
Release Notes Updated: May 12, 2017

Welcome to this release of IBM Aspera Drive. Drive 2.1.1 is a maintenance release that corrects a number of defects, provides enhanced proxy support for simplified enterprise deployments, and improves reliability in syncing with Aspera Files.


  • RSA keys are now supported. This enables transfers and syncing with Faspex and Shares installations that are hosted on nodes that do not accept DSA keys.
  • Users can now change the client-side resume suffix.
  • When configuring Microsoft Azure cloud storage, users can now use page blobs. In the Azure Storage Explorer, uploads using Drive appear as type Page.


ASDR-1159 - [Mac OS X only] A problem has been fixed that affected Drive on MacBook Pro 13- and 15-inch laptops that include the Touch Bar.

ASDR-1033 - An issue has been resolved involving drag-and-drop downloading of remote Faspex packages with Azure as the default file storage.

ASDR-1031 - When Drive is configured to sync with an Aspera Files folder, its behavior when that folder becomes unavailable has changed somewhat:
  • If a Drive user has set up Drive to sync with a shared Files folder, when that folder is no longer available (because, for example, the administrator has un-shared it), Drive now displays an error that directs the user to select a different remote folder to sync with.
  • If the Drive user had set up Drive to sync with a workspace that contains the shared folder, when that folder is no longer available, Drive now displays an error that directs the user to go to Files and remove the invalid folder link.

ASDR-1025 - Drive's sync feature did not work correctly when both HTTP and FASP proxy were enabled.

ASDR-1020 - [Mac OS X only] During the new-account setup process, Drive inaccurately displayed Shares account names as node. Now those account names are displayed underShares.

ASDR-990 - [Windows] You could not add a node account to Drive when an ISA proxy was configured.

ASDR-951 - [Mac OS X only] Drive crashed when the user attempted to add a Files account.

ASDR-881 - Drive could not upload to a node on Files with when the server required content protection.

ASDR-880 - Drive's sync feature did not work correctly with HTTP proxy.

ASDR-872 - Drive's sync feature ignored FASP proxy settings and did not use the proxy for transfers. (CIM-326)

ASDR-160 - Drive encountered the following error when transferring a directory via HTTPS fallback:
Error: One or more files failed (Code: 27)



On your Aspera Drive client:

  • Windows 7 with Service Pack 1 and IE 11; 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.


On your Aspera Drive client:

  • OS X 10.8, 10.9, 10.10, 10.11, or 10.12.

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.


Windows: AsperaDrive-
md5: ddac63cc5820a910d83e4134fcc82185
sha1: 2001e6b813b40d0c19a583ec9725eb39dc6888d8


Note: This release was developed using two different issue-tracking systems. For this reason, the list below uses two different formats for issue numbers.

ASDR-1034 - [Mac OS X only] Drive does not support NTLM. This means that using an ISA proxy with Drive is an unsupported configuration. A future release of Drive will include support for NTLM and Microsoft ISA.

ASDR-1032 - [Mac OS X only] If you upgrade to the current release from Drive 2.0.2, and if Drive is configured with both manually authenticated HTTP proxy and FASP proxy, you must re-enter the FASP proxy password when you re-launch Drive.

ASDR-999 - When Drive is configured with an ISA proxy, you cannot add new Drive accounts for Enterprise Server users with invalid certificates. This is due to the way the proxy validates certificates before the request reaches Drive.

ASDR-987 - Drive does not permit drag-and-drop transfers between shares.

ASDR-974 - [Windows only] When two users are logged in and one installs Drive system-wide, the other user sees an error message when attempting to open the Remote Drive until that user launches Drive.

ASDR-970 - Drive crashes if a large number of packages (>100) are downloaded and queuing is turned off. Workaround: Turn on queuing by going to Preferences > Transfers and selecting Enable queuing.

ASDR-953 - Drive stops Sync when disk space runs low, and will not restart after more disk space has been made available unless the sync selection is modified before restarting the sync.

ASDR-952 - [Mac OS X only] After a new installation of Drive with at least one account added, when you try to open the Services tab, Drive takes you to the Account tab. To stop this behavior, click settings for packages or Sync.

ASDR-944 - [Mac OS X only] The Send with Aspera Drive context menu may not be available if you select more than 1000 items on your local machine. Workaround: To send 1000 items or more, use the Send Files dialog.

ASDR-941 - When you drag and drop more than 125 files from your Faspex Inbox to your local machine, there is a delay of at least 30 seconds before the transfers appear in the Activitywindow.

ASDR-931 - [Mac OS X only] When you browse content in Drive's remote view with a Files, Shares, or Enterprise Server account, the display is limited to 1,000 files or folders.

ASDR-928 - [Mac OS X only] When you double-click a remote file to download and open it, if the file type does not have an application associated with it, the file does not open once the file has been downloaded. Workaround: Locate the downloaded file locally, double-click it, and select an application with which to open it.

ASDR-919 - [Mac OS X only] If the remote view remains open while you change the permissions on a shared folder, Drive does not detect the change in permissions. You must exit the folder and refresh the remote view to update permissions.

ASDR-851 - [Windows only] For Drive with Aspera Files: When a folder in your workspace and a folder shared with you in the same workspace have the same name, rename actions fail.

ASDR-840 - [Mac OS X only] When you add a Drive account for a server with an invalid certificate, Drive incorrectly does not display a security alert.

ASDR-768 - [Mac OS X only] You may encounter an intermittent "Authentication failed" error when Drive attempts to automatically download a large number of packages simultaneously to the Inbox. For best performance, queuing should be on and set to a low number (such as the default of 3). To turn on queuing in Drive, go to Preferences > Transfers, select Enable queuing, and verify the value in the Maximum concurrent transfers field.

ASDR-624 - [Mac OS X only] Zlinux nodes cannot be added to Drive.

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.

ADSR-576 - The Send Files window is slow to open if a Files account is selected.

ASDR-555 - Drive has a maximum screen resolution of 200%. If your screen is set to a higher DPI, some windows, fields, and buttons do not display correctly.

ASDR-520 - [Windows only] After you upgrade from Drive 1.3.0, if you use the Cortana assistance tool to search, Windows displays the older (1.3.0) Drive icon, rather than the newer (2.x) icon. This is due to an issue in Cortana.

ASDR-485 - [Windows 2012 R2 only] If you added accounts as an admin, the Drive context menu fails to appear when you right-click a file or folder.

ASDR-435 - [Mac OS X only] If you delete a synced directory during a sync action, Drive may display intermittent errors.

ASDR-414 - When you view a Faspex package in Drive's remote view (that is, within a file browser), if the package contains folders, you cannot open the folders. This is the case for Inbox, Sent, and Archived packages.

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-269 - When you use Drive with Aspera Files, you can download the contents of folders shared by others, but not the folders themselves.

ASDR-252 - [Windows only] When you use Drive with Aspera Files on Internet Explorer 8, the Files logo does not display correctly.

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.

ASDR-157 - [Windows only] Drive does not display all of your packages when you browse your Faspex account in Windows Explorer if there are several thousand Inbox and Sent packages.

#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 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 supports Aspera Shares 1.9.2 and higher. For SAML authentication, Drive requires 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 accesslist 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:
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.

#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.


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.

Powered by Zendesk