Release Notes: IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client 3.6.0 for AIX

Product Release: March 8, 2016

Release Notes Update: November 14, 2016


Welcome to the first AIX platform release of the IBM Aspera Enterprise Server suite of products (Enterprise Server, Connect Server, Point-to-Point, and Desktop Client).

Note: Release 3.6.0 does not include the following features that are standard in other platform versions of these products:
  • The GUI has not yet been ported to AIX. Transfers must be done using ascp on the command line, or, for Connect Server only, using the Web UI.
  • The Aspera watch service is not included.
  • The Aspera watchfolder feature is not included.


AIX: 6.1, 7.1


Enterprise/Connect Server

md5: 9a7b65d1e9f13a762d090dd1f1801ee6
sha1: 54cf114c14f38f6e33e8c5c770e7ceca673d36c5


md5: 650fae4c7e4e8ca2106186f728fbef5c
sha1: 3bc2efb444838f730e5a9a2c781b3f9581708ee1


md5: 6c73d752960da91e0b6a11531f746118
sha1: 3fd3094f7139d577227d3e6c04130a776faf7e63


Async on AIX does not support continuous push or bidi mode.

ES-131 (CIM-208) - The installer changes permission on some system-level directories.

#32934 - The Internet protection suite "Covenant Eyes" is k`nown to interfere with Aspera HTTP fallback by reading into memory an entire file's worth of data. When the file is large it causes timeouts and hangs.

#32680 - When a remote source does not exist, ascp leaves behind an orphan directory.

#32669 - When a directory is linked from a subdirectory, it does not appear in the search result.

#32627 - When a filename is just a dot and an extension, it is reported by the gen4 Browse API as a file with content_type "application/file_extension".

#32553 - When the FASP session log source file list exceeds 500 bytes and contains multibyte UTF-8 characters, the output is truncated in a manner that creates an invalid UTF-8 sequence.

#31791 - The user is unable to transfer files with the file extension .aspx. Workaround: Change the client resume-suffix configuration to an alternate value.

#31423 - It is possible for an ascp transfer of a file to a full disk to be reported as successful by both the sender and the receiver.

#31405 - The async documentation regarding timestamp modification use is incorrect. If the checksum is "none" when a file is modified and the file size stays the same, async will not detect the change, even though the timestamp has changed.

#30690 - ascp fails with an inaccurate message, "Error: failed to authenticate" when a server is configured to only accepts cipher that are no longer supported.

#29787 - When the docroot is not configured, the node API returns the HTTP error code 500 ("Internal Server Error").

#29078 - Gen4 node API: When an access key is created using the standard node user authorization, the access key inherits that node user and its associated system user. Afterwards, asnodeadmin can be used to associate a new system user to the node user, but the new system user is not updated for the access key.

#28939 - If command-line ascp neglects to specify a destination, the failed transfer (error: "no remote host specified") causes problems with Console.

#28887 - When a file or directory is moved using the --exclude option with async, the old file or directory is not removed from the remote side.

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

#28219 - asperanoded fails to delete a directory name containing backslashes. Workaround:
  1. Stop node.
  2. At the command prompt, issue the command ulimit -S -n 2048.
  3. Restart node in the same command-line window or shell (the limit is shell-specific).
  4. Send in the same /files/delete request as you did before; the head and everything in it will be removed.
Note: Prior to the command in Step 2 above, you can find out the current limit in a shell by issuing the command ulimit -a | grep "open files".

#27908 - When asperacentral has database errors, it continues to allow new transfers.

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

#27311 - Sync: An apply-local-docroot pull copies local docroot path into docroot path.

#27007 - Aspera clients on UNIX systems will use the HTTP_PROXY and HTTPS_PROXY environment variables when configured to use a FASP proxy. These variables are not used in HTTP Fallback.

#25127 - HTTP fallback temporary files (*.haspx) are not filtered out by the Node API.

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

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

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

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

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

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

#22044 - Sync: asyncadmin reports all sessions locked after the last actual running session.

#21629 - Connect Server does not accurately reflect file permissions for user actions.

#21604 - Extremely large socket buffer value causes overflow, resulting in an error when creating a UDP socket.

#21014 - When creating a file with vi during a sync, the swap file is in conflict.

#20906 - async can't create a watch on an unreadable directory; therefore it does not get notified when permissions change. In addition, async treats an unreadable directory as "skip" rather than reporting an error or conflict.

#20002 - Inconsistent behavior regarding symbolic link following: /files/browse doesn't follow the links and reports links and their target (final type and next name), while /files/info reports symbolic links as files or directories.

#19945 - asyncadmin creates SHM and WAL files for read-only operations. Once asyncadmin is run as root, an async run by the user does not have permission to access the existing SHM and WAL files and thus async fails. This is due to a bug in SQLite.

#18913 - Sync db logging: cancelled or stopped jobs are reported as "completed" in fasp sessions status.

#18780 - An async push conflict occurs when a new file is renamed quickly.

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

#18530 - FASP and Sync now accept and verify SSH remote-host keys.

#18402 - When an XML job greater than 1KB is submitted, the related message in syslog is truncated.

#18368 - Files with a backslash in the filename are not displayed by the Node browse API.

#16911 - Characters in the async session option that are not preceded by a "-" or "--" are ignored, therefore failing to trigger an error message. Any session options specified (such as -l or -a) after the string of characters not preceded by a "-" or "--" are also ignored. The session will still run, using the default values, without notifying the user that the new settings have not been applied.

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

#13761 - If filenames contain "\" or new line, async will try to transfer but fail, causing the internal transfer queue to become full and the synchronization to stall (or hang after all the other files have completed).

#13645 - When a directory is renamed during transfer, Sync continues running and never completes.

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


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.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk