Release Notes: Aspera Enterprise Server, Connect Server, Point-to-Point, and Client 3.5.1
Release Notes: Aspera Enterprise Server, Connect Server, Point-to-Point, and Client 3.5.1

Release Notes: Aspera Enterprise Server, Connect Server, Point-to-Point, and Client 3.5.1

  • Product Release: Sep 12, 2014
  • Release Notes Updated: Sep 12, 2014


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

  • New security-related aspera.conf options that may be used on server or client:
    • <ssl_protocols> to specify which SSL protocols are allowed, e.g. tlsv1, sslv3
    • <ssl_ciphers> to specify SSL ciphers allowed, e.g. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, etc
    • <fasp_macs> to specify message authentication codes allowed in fasp transfers, e.g. sha-256, sha-1, md-5, none
    The server can limit what it will accept, and the client can request a certain value. If the value is not allowed by the server, the transfer session will be denied.
  • Expanded support in the GUI, aspera.conf, and ascp for preserving timestamps and creation-time on both upload and download transfers with all supported cloud storage platforms (S3, Azure, Swift, and Google). The aspera.conf file and ascp use existing options for timestamp preservation. The GUI offers an option to turn on timestamp preservation when connecting to a cloud storage endpoint.
  • New optional transfer binaries a4send / a4recv are built on Aspera's next-generation architecture and enable ultra-fast transfers for very small files. The binaries are installable from MSI or RPM images and replace the standard ascp binary. Use of a4 is transparent to the user. It can do GUI transfers, ascp command-line transfers, and faspmanager API jobs. NOTE: In 3.5, a4 works in push mode only. (Pull support will be available in a future release.) DETAILS:
    • File metadata is sent via the data transmission path (i.e. via FASP) instead of via transmission control path (SSH/TCP).
    • The number of parallel I/O "worker" threads can be configured based on the native storage system characteristics (e.g. parallel file systems or slow NAS/CIFS/NFS),
    • The size of the data chunks that are read from disk is configurable.
    • Pipelined file I/O mechanism feeds incoming chunks through compression, encryption and transfer as they are coming in from disk.
  • Aspera Sync: New parallel transfer session option --transfer-threads allows a data set that will be synchronized to be split across multiple internal ascp transfer sessions. This allows maximum pipelining; for example, enabling "small files" to be deduped while large files are transferring. Syntax: --transfer-threads=n[:size] where n is the number of transfer threads (default=1), and size is the transfer threads' maximum file size.
  • Aspera Sync: New option for "LZ" compression. Syntax: --compression=mode, where mode is zlib or none (default=none).
  • Aspera Sync: Improved to support Windows applications that concurrently access files being sync'ed. This avoids sharing violations such as files open in multiple Microsoft Office applications.
  • Support for Keystone identity service with Swift, thereby allowing transfers to HP Cloud.
  • Verified ascp command-line support for cloud storage sources and destinations as URIs.
  • GUI: Added cancel capability on long running move or copy operations such as in cloud object storage.
  • Added delete capabilities to cloud storage benchmarking tool, axcloudcp.
  • A new ascp command-line option --apply-local-docroot option is equivalent to setting the environment variable ASPERA_SCP_DOCROOT.
  • New asperatrapd feature to disable directory creation on cloud storage, i.e. disable creation of zero-byte files denoting directories.
  • New server-side configuration options for symbolic link handling, including allowing/disallowing link creation, copying, and following. Previously these options could only be set on the client side. For details, see "Server-Side Symbolic Link Handling" in the admin guide. NOTE: This feature is not yet implemented in the application GUI, which still works the same as in 3.4.6. However, it is available through other components, such as Connect, Shares, Faspex, Sync, and ascp.
  • New capability for parallel uploads to S3 using the ascp option -C[1..N]. A new wrapper utility ascppar transparently initiates concurrent parallel transfers of a set of files or directories to S3. This is useful for maximizing speed on multicore machines (for example).
  • The save-before-overwrite feature (introduced 3.4.6) has been extended to take precedence over file_system/overwrite.
  • Improved error reporting for mysql operations in asperacentral.
  • More error logging from the pre-post processing script.
  • Finalized support for the Azure external token service.

Other Changes

  • Aspera Sync: The inode-format option has been discontinued in favor of managing all file path references in the async snapshot by pathname (to avoid issues with unstable inodes).
  • The aspera.conf settings <preserve_mac_xattr> and <preserve_mac_xattr_storage> are no longer supported. If they are found in aspera.conf, they are rejected with an explicit warning message. The feature has been removed from ascp 3.5 and has been replaced with the async aspera.conf settings and command-line options for preserving xattrs and ACLs. For details, see the Aspera Sync User Guide 1.5.6 or later.


#11268 - When HTTP fallback transfers are interrupted, Console still shows the session is running.

#11889 - The filenames and content of the default mail templates are not localized.

#11890 - Configuration dialog is not internationalized.

#16209 - On the Details tab in Point-to-Point on Windows (in Korea), the GUI shows negative number for file size/transferred.

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

#16971 - In SOAP queries, ExpectedFileCount and FileCount return inconsistent values.

#17386 - asperanoded - group docroot inheritance does not work.

#18021 - asperahttpd does not support certificate chain file.

#18216 - Ascp is logging up to 99 messages/second of the type “Log queue: 100 GB already queued, delay queuing more”.

#19298 - 3.1 Client to 2.6 server fails (session stats) although session status=success.

#19806 - Faulty ascp (putty) ssh-agent interaction.

#20643 - Translation of source string “Frame Address is invalid: Illegal address” is incomplete. “Illegal address” is still in English.

#22256 - Unable to authenticate to isilon cluster docroot on 2.7.4 Windows Server with 3.3.0 client.

#22902 - UAC XML Parser blows the stack on windows if there are more than 950 tags on the same level.

#23053 - Some EAR downloads (downloaded in encrypted form) fail with server noting "file modified or truncated: Disk read failed"

#23097 - faspcat fails to read aspera.conf for file mode settings <directory_create_mode> and <file_create_mode>.

#23324 - Error/conflict mismatch with Office files.

#24430 - The .partial file remains at the destination after the source file is modified and the upload is complete.

#24752 - Node daemon does not send HTTP code 100 (Continue).

#25168 - Wrong ascp error message on trapd failure.

#25226 - Aspera version of libssh2 does not detect EVP_aes_128_ctr correctly.

#25488 - Aspera Central: Transfer and Rename using Job API is not consistent.

#25636 - S3: 256MB chunk size causes transfers to hang for some time.

#26250 - Transferring with hot folders to an AMI with an S3 docroot gives an access denied error: "you have attempted to create more buckets than allowed".

#26648 - Mac async has problems sync'ing ._ files (xattrs).

#27462 - Console reports inconsistent transfer size when symlinks are used.


#3476 - When uploading to Linux from a Windows client to a folder called dir\ , pressing the Upload button fails to open the dialog to select a file. When uploading to folders called dir” or dir? or dir”: the file is not transferred, but Connect reports a status of “Done”.

#3522 - The aspera.conf.websample from ES 2.1.3 does not get converted on upgrade.

#4822 - Installing ES 2.5 on a machine with a pre-installed cygwin gives 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 - In OSX, the desktop clients 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 will be 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. WORKAROUND: 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

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

#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 of 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. Even though 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 will 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 admins/users who installed Aspera Enterprise Server on Windows XP and specified a service user -- for example, svcAspera -- rather than a local system account.)

#17386 - Group docroot inheritance does not work (related to asperanoded).

#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 clock moves backwards.

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

#20856 - Apache 2.4.4 bug. The htpasswd command given in the Connect Server guide may not work. WORKAROUND: Provide the password on the command line, as described in the workaround given in the Connect Server guide.

#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 privileges of the user running IIS and we are not able to query 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 ES 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, and 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 will generate a "no such file" error for any already-transferred files.

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

#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 IE brings up a login window where the username field already has the string "user_name" filled in.

#24430 - A .partial file remains at the destination after the source file is modified and upload is complete.

#24549 - Drag-and-drop with 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 - Release notes for ES 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 is logging 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.

#24752 - Node daemon does not send HTTP code 100 (Continue).

#24838 - Unable to upgrade to Connect Server from Enterprise Server on Windows. The Connect Server doc 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/sync'ing 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 failed 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.

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

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

#26379 - Google Scp: hot folder table display 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 - Pvcl-trap - Need to limit the number of buffers used for uploads.

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

#26480 - Node API - transfer stuck in idle status when no one is listening to mandatory management port.

#27056 - No ascmd support for server-side symlink configuration, which means 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".


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, Kernel 2.4 or higher and libc version GLIB 2.3.4+.

Mac OS X: 10.7, 10.8, 10.9

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


Enterprise/Connect Server

Windows: AsperaEnterpriseServer-ML-

md5: 271c8f27d46a0710ab1f5c84ac5ed0e4
sha1: 694ecb413d6d1990c338f8432b7e14f897984cda	

Linux 64-bit (rpm): aspera-entsrv-

md5: eb9a1e672bc1f2128794e5ae9bb23431
sha1: 2800f0cfb650d50f611d904e18e25d1ac1459b62	

Linux 64-bit (deb): aspera-entsrv-

md5: cef167323b2c3e1006cfe4a555c921c3
sha1: b49afa94f934d020f97523fbb298b4dcdfbebea5	

Mac OS X: AsperaEnterpriseServer-

md5: 7f33ba5022c3a5547572896daf7d4c11
sha1: 256f0af8c1c81f575e6916c2a96920373bc7019a


Windows: AsperaP2P-ML-

md5: 303c1571d39df914ecb75f1f71c9109b
sha1: 3e3d0a8e3bc32a94414c09b576d7d461a636a649	

Linux 64-bit (rpm): aspera-scp-p2p-

md5: 196cea48b0758d318cf1c3275ae81c4c
sha1: ff393993747bd80012665bf8db94b7ed69766e20	

Linux 64-bit (deb): aspera-scp-p2p-

md5: a65e13eaf66355d1cc32a9994ef453b2
sha1: 9d56be8413a2244f216ada0d3d75a7e21b1cbbe1	

Mac OS X: AsperaPointToPoint-

md5: ca413f539803b34184a34e9c142e3c7a
sha1: 1689c6011efe386850f9a893b210f8840be892cf


Windows: AsperaClient-ML-

md5: fc61509ccf891086ca89d440b1f39a27
sha1: 3f7ebb993ae63f3b5f6ee232455c2fd4e9731844	

Linux 64-bit (rpm): aspera-scp-client-

md5: 5fe0068a435af2efcf3f70d0ebb07adb
sha1: 9e22455b72b7ccf69671a62e6afb635a8bfe40ee	

Linux 64-bit (deb): aspera-scp-client-

md5: 5475e0f6d52c3751651e672739fd4b29
sha1: c7dbf5c8da8a56e270cdcf4bb12cfe02c110b4e0	

Mac OS X: AsperaClient-

md5: 2061fded200be756a56714ce8e787681
sha1: a2d08ae22bf774e956a7c6758945abbd5d9a163e


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.