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

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

Product Release: Jun 27, 2014
Release Notes Updated: Jun 27, 2014


Release 3.4.6 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.4.6 includes Aspera Sync 1.5.6.

New Features

         A new configuration parameter <enable_sslv2> can be used to disable SSLv2, but only for the Node API—not for HTTPS fallback or Connect Server.

         Users can now select a custom look and feel for the GUI in order to solve some remote desktop and screen-sharing issues under slow connections. For details, see the KB article How to Set a Custom Look And Feel in the Aspera GUI.

         Enterprise Server, Connect Server, Point-to-Point, and Client have been updated to OpenSSL 1.0.1h.


         #25334 - asconfigurator duplicates entries for domain users in a group file.

         #25397- Node crashes when deleting directory with corrupt contents.

         #25910 - External authorization client (asperacentral) timeout issue on Windows.

         #25941 - Absolute path revealed in error message (that is, portions outside the docroot).

         #26005 - When alee registers for the first time, its status is shown as inactive, even though registration was successful.

         #26065 - "Strong password required" ignored with HTTP fallback upload + EAR.

         #26105 - Enterprise Server logs show password.

         #26128 - Trap: stat when many partial files leads to transfer initiation failed.

         #26160 - asperanoded reports the default docroot instead of the user’s docroot.

         #26175 - Trapd failure during session establishment when there is a large number of concurrent sessions.

         #26180 - On Azure, storage passwords are being stored in the central database and can be retrieved through the Node proxy on Azure.

         #26197 - The session cookie is missing the HttpOnly attribute, creating vulnerabilities to hackers.

         #26268 - Segmentation fault in high concurrency uploads to S3.

         #26269 - The desktop application displays wrong source and destination paths for transfers to Shares.


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

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

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

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

         #26329 - The ascp -resume suffix (.aspx) is now excluded by default.

         #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


         Windows: XP, 2003, Vista, 2008, 7, 8, 2012

         Linux: Kernel 2.4 or higher and libc version GLIB 2.3.4+


         Enterprise Server 3.4.4 Release Notes 

         Enterprise Server 3.4.3 Release Notes 

         Enterprise Server 3.3.4 Release Notes 

         Enterprise Server 3.3.3 Release Notes 

         Enterprise Server 3.3.0 Release Notes 

         Enterprise Server 3.1.3 Release Notes 

         Enterprise Server 3.1.0 Release Notes 


Enterprise Server and Connect Server


35a8ee7b0145de802a5f8de3ab2f55ce  aspera-entsrv-

c47adae9f0f447c15f823bb9873d8b0a  aspera-entsrv-

fa02c3881ece0730d4db717ac994548c  aspera-entsrv-

67dfbc88beadbfad8d579426f60bda5c  aspera-entsrv-

992ca626ed5f7972d220bd19953f68eb  AsperaEnterpriseServer-ML-


67d491c7f8a4f989e0ab351e37449a7d187322ba  aspera-entsrv-

6b444f9c9067d7306f1d2f1987074d1e92acd773  aspera-entsrv-

e903f6c6fc051f49a2430435d9c946fd7778dc4d  aspera-entsrv-

c21604c89182675317e969d8ca3d9501b73e42c5  aspera-entsrv-

a0ea9a408609ae4207b9802cc84a513592e5f06f  AsperaEnterpriseServer-ML-



8c49fe9346731b091a6e574b2825aa3a  aspera-scp-p2p-

8278873943bba8163b5a135a30c70ae6  aspera-scp-p2p-

882a80f1b4f6f4ff881d4c95c630c537  aspera-scp-p2p-

2671cc09fc6c7f662c1dd9745d85682a  aspera-scp-p2p-

5df48ecaffc169f5f349495791b26c04  AsperaP2P-ML-


2060f757ad7d85e1436b32b6f5ba53245e58c149  aspera-scp-p2p-

5114c82fc256b09a63a1dbd47a62b79ce7965dd3  aspera-scp-p2p-

18bc1ebffa1d053fcba2a573c21ec7b92642c764  aspera-scp-p2p-

fed32ed6c1c034307a0c67a7e3285599d376e956  aspera-scp-p2p-

eeee67c5abbd0e559fa2aa51ede1f801186a3563  AsperaP2P-ML-



c5b80b04674101abbb93aee06890519e  aspera-scp-client-

07352f6843d264b4b2635f5ce198b936  aspera-scp-client-

4389e6383891560bbc08b5d6bb6d2cec  aspera-scp-client-

9e36c1fdc31c63a12608e7ff2d8d29fb  aspera-scp-client-

1b443df7607762df032173d282e7c877  AsperaClient-ML-


dbc3692156d0cd296419a11dc9a4cc2e747f3ffa  aspera-scp-client-

5d54d1a20819bca6d53ba7d3b00e3879fe1537a6  aspera-scp-client-

7b55e8229b1e24a2310817a4bbdb7a6d346c83bf  aspera-scp-client-

9fb74f36ff784410386cdc47c4438dceac38af8d  aspera-scp-client-

854b6ddcca93f5bca9f2fb4f97e0b5593c6e466c  AsperaClient-ML-


         Enterprise Server 3.4.6 User Guide (Windows) 

         Connect Server 3.4.6 User Guide (Windows) 

         Point-to-Point 3.4.6 User Guide (Windows) 

         Client 3.4.6 User Guide (Windows) 


         Enterprise Server 3.4.6 User Guide (Linux) 

         Connect Server 3.4.6 User Guide (Linux) 

         Point-to-Point 3.4.6 User Guide (Linux) 

         Client 3.4.6 User Guide (Linux) 


For online 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 Aspera’s regional support centers.