IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.5.4
Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.5.4

Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.5.4

  • Product Release: Feb 26, 2015
  • Release Notes Updated: Feb 26, 2015


Release 3.5.4 is an update of IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client, and provides the new features, fixes, and other changes listed below. Release 3.5.4 includes IBM Aspera Sync 3.5.4.

New Features

  • Strict token authorization when using an Aspera web public key.
  • Checksums, when enabled, are now logged. Modification time (mtime) is also now logged.
  • With uploads to Limelight, modification time can now be preserved (but not access time or creation time).

Other Changes

  • SSLv3 is now disabled in the GUI.
  • Software and documentation are now in compliance with IBM naming conventions, copyright notices, and trademark notices.


#26626 - The resume-partial-transfers feature does not work when EAR is set (download).

#27664 - Transferring a small number of files totalling over 100 GB causes high CPU usage (~100%).

#27994 - For Akamai storage, the rename option is disabled.

#29145 - The ascp bandwidth measurement is not displayed on the local client.

#29222 - When using drag-and-drop to transfer a 64+ MB file to a different folder, only the file manifest moves.

#29314 - The hot folder feature "Send Changes Daily at" does not work.

#29415 - For Limelight, multipart "success" has to be polled after completion.


Windows: 7, 8, 2008r2, 2012

Linux 64-bit: RedHat 6-7, CentOS 6-7, Fedora 16-20, Ubuntu 12-14, Debian 6-7, SLES 11-12 Kernel 2.4 or higher and libc version GLIB 2.3.4+.

Mac OS X: 10.7, 10.8, 10.9, 10.10

Browsers: Internet Explorer 8+, Firefox 27+, Safari 6+, Google Chrome 32+


Enterprise/Connect Server

Linux 64-bit (deb): aspera-entsrv-
MD5:  e331ee395dfe7178e9d9accfcdf8c6d3
SHA1:  e0c417a1b8406d53d43af2504ee34152f931266a
Linux 64-bit (rpm): aspera-entsrv-
MD5:  68eea2237f0d70f74ff91dd67ab79969
SHA1:  26b6e7135b98a14a99285bf15ecf8c21f921425f
Linux 32-bit (deb): aspera-entsrv-
MD5:  6d2eb49819779b97025ebe21291992ce
SHA1:  a098899b7e16e748b20a24536b3b6b954e08badf
Linux 32-bit (rpm): aspera-entsrv-
MD5:  1ece0a46e3cba2be79f9145f091fb8be
SHA1:  88c056a09d7bd75792284055157e2dcd960f0e68
Mac OS X: AsperaEnterpriseServer-
MD5:  cf99088ec05b2dc1b9d08885883ed27f
SHA1:  92757ff13a74d9a24ae34de30e44a515acf0343b
Windows: AsperaEnterpriseServer-ML-
MD5:  3b08aea5de4ad03fc03d2803b53d83f4
SHA1:  deb01fce43633be44d8c2aef9e385ac4d889c8d1


Linux 64-bit (deb): aspera-scp-p2p-
MD5:  b4410c1ea9c15ba02249641a9425d49c
SHA1:  3922de2c80c852eb2b2d755dc1c8839b57847d6a
Linux 64-bit (rpm): aspera-scp-p2p-
MD5:  7f59629a087f149dfddcc3d075a5ff04
SHA1:  ba36627a971aebdeced1f148afabbd4faa2f8bd3
Linux 32-bit (deb): aspera-scp-p2p-
MD5:  4e0683b13c5b42f6835287ab80c362f9
SHA1:  7a0df93bf36104420f6b2114bc8dd896e9285660
Linux 32-bit (rpm): aspera-scp-p2p-
MD5:  340f3a1161b3629f9408a508e4e7d865
SHA1:  4133cb4c97e9c80771ffcd6e89241de6fa682716
Mac OS X: AsperaPointToPoint-
MD5:  24680cedaf185162fe35e0f98be5a264
SHA1:  3614b842c25f487f43502cb31e06af4e38ccc0b4
Windows: AsperaP2P-ML-
MD5:  2702b8a79162a1374f2a6693b812a504
SHA1:  baa671a7d9585c6bc794b350f5951a4357f29b7c


Linux 64-bit (deb): aspera-scp-client-
MD5:  31fff38e8d094ca2c9a3c5076d5cc548
SHA1:  611cdcf0b804cf2e59fd7d2cfbd289479286cb2f
Linux 64-bit (rpm): aspera-scp-client-
MD5:  918e0c5ceddb07bb7968626711a1faec
SHA1:  9a1c4802bff645b4703cf330211238e4db9f1e68
Linux 32-bit (deb): aspera-scp-client-
MD5:  30e8c9a6289772d643cd8885305009b8
SHA1:  68bb12c70eb19956b2fabbb3a4b2181e7cce3ae4
Linux 32-bit (rpm): aspera-scp-client-
MD5:  b040dd6abc04391362af44ead27255c6
SHA1:  3273594414c35439459510ffa1bc4d68a6969f0f
Mac OS X: AsperaClient-
MD5:  6f786be4ed368d2c610f01b840cace62
SHA1:  c420acc47db4428e123e8a18d0d6c132404e73d1
Windows: AsperaClient-ML-
MD5:  29336f7c60cca2aa376706c194a95946
SHA1:  e0613a466f214a43a664eb9e7c90972f0308d69c


#3522 - The aspera.conf.websample from Enterprise Server 2.1.3 is not converted on upgrade.

#4822 - Installing Enterprise Server 2.5 on a machine with a pre-installed cygwin gives an error message, and OpenSSH does not start.

#5079 - Public keys created with 2.2.1 are not installed in the proper directory; as a result, an upgrade to 2.5 may fail to find existing keys.

#5210 - In the desktop client, the File Manifest Path setting does not work with paths containing commas.

#5442 - On OS X, the desktop client's remote file browser hangs on a directory containing over 25,000 files (out of memory).

#5713 - The Windows installer cannot install to a customized folder whose name contains Unicode characters.

#6302 - Connect Server on Windows does not support Unicode user names.

#6358 - Hot folder transfers fail with Unicode user names.

#6443 - If admin A creates a new hot folder and exits the desktop client, and then admin B exits, the new hot folder created by admin A created is lost.

#6448 - When your regional and language options are set to language standards and formats that do not use "." to represent the decimal point, values are displayed inconsistently using both "." and the native character to represent the decimal point.

#6453 - In the desktop client, changed Preferences settings are not updated under Configuration until the desktop client is restarted.

#6598 - Starting/loading the GUI via SSH-tunneled X redirection takes too long to respond.

#7271 - Sending a file with ":" to Windows causes the creation of an alternate stream. In addition, when partial is enabled, the stream name will remain .partial (the rename to the final name does not work).

#8351 - Failed file paths are truncated to 128 characters.

#8495 - Hot folders do not support the root drive (for example, C:\ or D:\) as the source path. Workaround: Change the source path to point to a subdirectory.

#8534 - IPv6 requires ascp to have the -6 option, which is currently disabled on the server side if the user is configured for aspshell.

#8538 - If a file fails to be renamed from .partial after it transfers, the transfer is still considered successful and the session will continue (with additional files being renamed successfully). The receiver side logs an error message, but no error is logged on the sender side. Successful transfers that were not properly renamed from .partial should be manually renamed.

#8620 - Enterprise Server for Linux fails to install if the dependency perl(CGI) is not installed. Workaround: Install perl(CGI), then rerun the Enterprise Server installation. For example, to install perl-CGI on Fedora, run yum install perl-CGI.

#10157 - Connect Server: The Change User button feature (<EnableUserSwitching> in aspera.conf) does not work on Mac if the login credential is saved into KeyChain.

#11550 - If preserve_attributes is set to none on the server side, when downloading a single file with the -p option, the file has an invalid atime value.

#11551 - Group settings under Server Configuration are not being inherited by the group members.

#12854 - The maximum upload size for S3 storage is limited to 625 GB.

#12972 - A log message is no longer generated for prepost execution.

#13450 - The -C option does not work for special storage (docroot or direct).

#15897 - From the AWS S3 console, it is possible to rename a folder to have the same name as an existing file. From the desktop client GUI, the folder and file are displayed with the same name. However, if you attempt to download the folder, the file is downloaded instead. Also, uploads to the renamed folder do not complete successfully. Although it appears in the desktop client that they have completed, the uploaded files are not available at the destination.

#16390 - Unicode filenames appear incorrectly in pre/post-processing email notifications.

#16517 - Hot Folders are unable to detect Microsoft Word and PowerPoint file changes.

#16671 - The Change User button does not work in Safari 6.0.

#16694 - S3 uploads do not resume if the PMTU changes.

#16884 - Resuming a file transfer to S3 starts from the beginning if the destination file already exists.

#17106 - Windows displays dot files, as well as Mac xattr files.

#17218 - On Windows 8, the delivery confirmation receipt is not readable or deletable.

#17243 - An S3 download fails when a filename contains square brackets or a caret.

#17318 - When upgrading, "Run Aspera services as a local SYSTEM account" is enabled by default. In order to preserve the service user from the previous version (for example, svcAspera), you must disable this checkbox. (This applies to administrators or users who installed Aspera Enterprise Server on Windows XP and specified a service user -- for example, svcAspera -- rather than a local system account.)

#18659 - Searching with very long pathnames (over 520 characters) results in an "insufficient buffer space" error.

#18832 - Windows Network hot folder stops scanning for new files when the clock moves backwards.

#20511 - Connect Server 2.6.3 allowed docroot to be a symbolic link, but 3.1+ does not.

#20576 - Target Rate must be in the range 0 -100 if TargetRateAsPercentage is yes; however, setting a target rate greater than 100 does not return an error. (Note that rate percentage is a deprecated feature.)

#20617 - The SOAP API does not return an error when invalid values are passed into any of a number of parameters. Instead of returning an error, a transfer is either created with a default value, or the bad value is passed to ascp where it will fail.

#20779 - The Connect Server web UI does not respect Groups configuration settings on Windows Server 2012. It restricts the privileges of the user running IIS, and does not allow you to query the group membership of the logged-in user. As a consequence, aspera.conf group settings do not apply.

#22552 - The Node API browse call returns file system details using a non-existent transfer user on WinXP.

#22618 - The behavior of the Node API "paths" filter changed with Enterprise Server 3.4. It now returns only the directory matching the filter, not the directory's content.

#22619 - In the Node API, file searches now follow symbolic links.

#22848 - On S3, uploading a file to a non-existent destination path, and without the -d option, creates the destination path anyway.

#22905 - On S3, when copying a file with ascp, if a slash is appended to the destination -- for example, /path/ -- the file is renamed path/. Because of the trailing slash, it appears to be a directory, but is actually a file.

#22998 - If the overwrite setting in the server's aspera.conf is "deny", a destination file with the same name as the transfer file is still overwritten.

#23070 - If a transfer of several files is interrupted, the retries generate a "no such file" error for any already-transferred files.

#23246 - Warnings are not generated about files skipped due to source base setting.

#23337 - An invalid payload for Node API *load_setup does not return an error.

#23434 - Node API: Files that start with "._" are not returned by the Node API browse action.

#23503 - Akamai: Uploads of zero-byte files appear to be successful, but no file is present at the destination.

#23583 - Certain option values for asperacentral job submission are case-sensitive.

#23791 - When faspcat forwarding is enabled, faspcat does not read aspera.conf for file permissions mode.

#23876 - On S3, when "always overwrite" is set, files are missing at the destination.

#24179 - In Connect Server, clicking change user in Internet Explorer brings up a login window where the username field already has the string "user_name" filled in.

#24360 - When a user has either incoming or outgoing transfers (or both) set to deny, the server issues an internal server error when the user attempts to browse the docroot.

#24549 - Drag-and-drop with the Linux version of the desktop client is not supported. Attempting a drag-and-drop upload does nothing. Attempting a drag-and-drop download causes the mouse cursor to display a plus sign, suggesting incorrectly that the feature is available.

#24638 - The release notes for Enterprise Server 3.3.0 say that with the new Node API, "Support for async session set up on behalf of client". No API for this is available.

#24671 - DB logger logs each file twice when the transfer is between a source and destination that are on the same node.

#24690, #23516 - On certain versions of Fedora Linux, the desktop client can fail to start or exits suddenly with an "assertion failed" DBUS error. This is rare but can occur.

#24838 - Unable to upgrade to Connect Server from Enterprise Server on Windows. The Connect Server documentation says you can do this from Control Panel > Add or Remove Programs as long as IIS has been configured. However, an error message tells you to create a website in the IIS manager, even if the website already exists. Workaround: Uninstall Enterprise Server, then install Connect Server.

#25042 - In the server-side aspera.conf, the none option for file checksum reporting is no longer supported; only md5, sha1, and any are supported. The any option means allow the checksum format to be whichever format the client requests. On the client side, the none option is still available, as a command-line option. A setting of any on the client side results in an error with the message "ascp: unknown file checksum type any".

#25083 - When hot folder transfers fail due to lack of permissions, the hot folders tab gives no indication that the failures are due to insufficient permissions.

#25631 - When transferring from Windows to Mac using preserve-acls=native and remote-preserve-acls=native, ACL data is saved as xattr. Workaround: Do not use the "native" setting when transferring/syncing across platforms.

#25636 - To use a larger chunk size to transfer big files to AWS S3 storage, some users modify the memory settings in the trapd initialization script, If you do so, be sure to preserve the script manually during upgrades to prevent it from being overwritten.

#25791 - Azure: Concurrent upload fails with the error "Data transfer stalled, timed out".

#25832 - Hot Folders: When creating or modifying hot folders, some controls in the File Handling tab do not work correctly:
  • The option for resuming incomplete files does not work, but is still necessary to enable options for checking whether files at the source and files at the destination are the same.
  • Selecting Compare File Attributes only checks whether the files are the same size.
  • Selecting Compare Sparse File Checksums actually compares full checksums.

#25865 - Allowing symbolic links to be copied also allows access to locations outside the docroot.

#25897 - The files counter increases when a file is still being moved to the source folder.

#25913 - Aspera Drive attempts to sync a file that is still uploading to Shares, resulting in a file error.

#25915 - When the sync function is set to continuous, overwriting an existing file on the initiating node may result in the deletion of the previous version of the file on the responding node. Workaround: Perform the sync manually to recreate the deleted file.

#25979 - The following error message may appear on Windows: "JET RUNTIME HAS DETECTED UNRECOVERABLE ERROR". The problem is caused by a mismatched DLL, which may result when an Aspera product upgrade is incomplete. To correct the problem, uninstall the Aspera product, manually delete the "bin" and "lib" directories from the Program Files Aspera installation directory, and reinstall. Another possible cause is bad system DLLs that may have been replaced by your antivirus system. To correct, uninstall the antivirus package and make sure the problem no longer occurs.

#26185 - During an upload to S3 storage, an error may result if ascp reports a successful file transfer before the transfer to S3 completes.

#26379 - Google Scp: The hot folder table displays incorrect format and data.

#26386 - Google: When there are concurrent uploads, some are stopped due to "Data transfer stalled, timed out".

#26427 - Akamai: Some concurrent transfers are stopped with the error "Insufficient Permissions".

#26446 - When there is excessive (> 90%) loss on a transmission channel, ascp may use an increasing number of buffers, impacting other transfer sessions and stalling the platform.

#26481 - Node API cannot modify a transfer with a put request.

#26480 - Node API - Transfers can become stuck in the idle status when no one is listening to a mandatory management port.

#26618 - The ascmd process does not exit properly on newer versions of SLES (SUSE Linux Enterprise Server).

#26631 - The Enterprise Server package needs an updated template license to make it work with entitlement-enabled Faspex and Faspex clients like Cargo, Outlook, and Faspex Mobile.

#27056 - There is no ascmd support for server-side symlink configuration, which means that the application GUI functionality is still the same as in 3.4.6. (For additional information, see the WHAT'S NEW description of new server-side configuration options for symbolic links.)

#27218 - If Shares is set to use EAR, downloads of unencrypted content via HTTP fallback will fail with numerous errors. Common errors include: "Insufficient permissions", "Server refused request", and "Connection Lost".

#27755 - When the network is busy, the FASP SSH session may close rather than retrying as expected, resulting in an error message, "Failed to send Close Session".

#27879 - always_set_home does not work if the user's home directory does not exist.

#27924 - Installing on CentOS 7 on Google Cloud requires that perl and the perl module Data::Dumper be installed first.

#28384 - OS X requires "Legacy Java SE 6 runtime" (Oracle's do not work).

#28288 - When the FIPS mode in aspera.conf is set to true, ascp fails with the error message, "ascp.exe: failed to authenticate, exiting.", without prompting the user for a password.

#28310 - Downloading a folder containing multiple large files from S3 fails to complete when using ascp -C.

#28629 - In Enterprise Server, asperanoded sometimes crashes.

#28630 - Some transfers to Akamai NetStorage have experienced high packet loss. A fix from Akamai resolves this issue; contact your Akamai representative.

#28747 - Connect Server security: Encryption over HTTP is not enforced, and must be set on the server by an administrator.

#28817 - The Aspera sync log entry for SYNCERROR_DELAY does not include information describing the file name and path.

#28820 - The following operations attempted in a Limelight directory fail or are unacceptably slow: copy/paste file, rename file, delete folder.

#29025 - For files in S3, async hangs when a filename contains special characters, such as the space character or double quotation mark (").

#29038 - The default checksum behavior with S3 (as with any cloud storage) is "none". An existing file on S3 is considered identical to the local file when their sizes are equal. Therefore the file on S3 is not overwritten, even when the content of S3 differs from the content of the local file. Using overwrite=always does not overwrite the file.

#29138 - For files in S3, the node daemon does not return the correct file modification time.

#29172 - When using --file-list or --file-pair-list with Softlayer, some files may not be transferred.

#29187 - For content in cloud storage, the Node API does not display all the files in the docroot directory. Workaround: Use the /files/info request to browse the docroot directory when content is in cloud-based storage.

#29255 - Download from SoftLayer of a file larger than 62GB is unsuccessful. Workaround: Do not use time-stamp preservation with SoftLayer.

#29372 - In a Connect Server installation using an Isilon cluster for storage, some icons and checkboxes expected in the directory display are missing.


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.