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

Product Release: September 30, 2016
Release Notes Updated: November 7, 2016

This release of IBM Aspera IBM Aspera Enterprise Server, Connect Server, Point-to-Point Client, and Desktop Client provides the new features, fixes, and other changes listed below. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. These release notes also list system requirements, including supported platforms, and known problems.



  • The performance of the FASP protocol has been enhanced. Compared to prior releases, unencrypted CPU-bound transfers may see an increase of up to 100% in overall throughput; and encrypted CPU-bound transfers may see an increase in overall throughput of up to 20%.
  • Resume mode checks in Ascp now use a SHA-2-based MD5 checksum algorithm by default; to configure alternative algorithms, there is a new aspera.conf option.
  • Ascp now features new complete include and exclude filter options to support glob and regular expression matching, equivalent to include/exclude options of async.
  • A new FASP Manager API feature can be used to send an event when individual arguments, such as directories in persistent sessions, are completed.
  • Ascp now includes a new asynchronous “in transfer” post-processing engine with Lua scripts. (This is the first version of this feature, and somewhat experimental.) A Lua interpreter engine is packaged with Enterprise Server, allowing for post-processing, validation, and authorization functions through embedded Lua scripts. Scripts execute asynchronously, and their progress is reported through a new validating state in the transfer session, without delaying completion of the file transfer or slowing the transfer pipeline.
  • Parallel (multi-session) transfers initiated from the command line can now use a URI for the filepath.
  • The <file_create_mode> configuration in aspera.conf is now respected when the docroot is a file URI.


  • a4 now ships pre-installed in the bin/ directory of Enterprise Server, Point-to-Point, and Client.
  • New options parallelize all file operations with a configurable number of threads for directory traversal and file attribute checking, as well as read/write.
  • Transfers to AWS S3 and S3-compatible storages are now supported.
  • a4 now includes support for all file resume, skip, and overwrite options of standard ascp, including the following:
    • -k0, -k1, -k2, etc.
    • always overwrite; overwrite if newer and different; overwrite if newer
    • resume based on attributes, sparse checksum, and full checksum
  • The preservation of file owner uid and gid (--preserve-file-owner-uid, --preserve-file-owner-gid) is now supported in a4.
  • Support for FASP management APIs is complete, including cancel actions and correct reporting of transfer direction, skip offset, and session errors.
  • a4 features a new FASP Manager-I/O interface to support byte stream (“streaming”) transfers. This support includes stream-to-file and stream-to-object storage transfer over WAN at high speed. The received stream output can write directly to object/persistent storage (S3-compatible APIs, Hadoop); and ingest supports large numbers of concurrent client sessions.
  • Transfers of empty directories, including to S3 APIs, are now supported.
  • Transfers of sparse files are also now supported.

Node API

  • A new case-insensitive filter can return filename matches regardless of case to Aspera Files.
  • The /ops/transfers API has been improved, including new support for setting transfer rates, bandwidth priorities, and pausing/resuming/canceling active transfers.
  • Asperanoded includes improvements in the /info and / API response, such as support for content protection settings.
  • /ops token authorization now uses SHA-2 as the default checksum, rather than SHA-1.
  • The status of files and transfers can now be reported by iteration token from the Node API. For example, if the user specifies an iteration token to https://node:9092/ops/transfers?iteration_token=1234, files and transfers from iteration_token=1234 to the present are displayed.
  • File modification events, including delete and rename, are now logged to redis/scalekv.
  • Transfer and bandwidth statistics are self-cleaning for large numbers of sessions.
  • Default and allowed SSL ciphers have been updated to eliminate support for 3DES and to align the defaults with hardened versions.
  • Users can now run asnodeadmin --db-update to migrate data from Enterprise Server 3.5.6 and earlier versions.
  • Asperacentral has a new raw options capability that allows users to authorize the use of raw format ascp options in raw format by configuring aspera.conf.

Watchfolder and Aspera Watch Service

  • The API call getWatchFolderState now returns the state of asperawatchfolderd in addition to the state of the transport and state of the watch.
  • Users can now select an existing asperawatchfolderd service when creating a watchfolder.
  • Watchfolder uses two new APIs:

    • asperarund: to start, stop, and manage asperawatchfolderd and asperawatchd under various user accounts.
    • access_control: to configure user access to specific instances of asperawatchfolderd and asperawatchd regardless of their system user account. See Breaking Changes for more information on this feature.
  • asperawatchfolderd now supports force-send-after configuration for growing files.
  • The configuration of asperawatchfolderd can be updated without re-sending the remote host password.
  • Watchfolder can now retry failed drops.
  • This release features many enhancements to the robustness of asperawatchfolderd:
    • The system ensures that a custom watchfolder aspera.conf is passed to ascp.
    • A valid and consistent docroot is verified upon startup.
    • --scan-period is now respected in creation.
    • aswatchadmin no longer hangs on removal of a watchpoint with a large number of files.
    • Archive directories are now respected.
    • Statistical counters persist after reboot.
    • asperawatchfolderd includes improved health status reporting.
    • Session cookie and tag fields are accepted and reported through management.
    • Timestamps are preserved when so configured.
  • Encryption-at-rest is now supported.
  • asperawatchfolderd now initiates transfers with a destination root, allowing Watchfolder transfers to work using the Aspera upload option for Akamai storage (requires a minimum server software version on the Akamai side).


  • Access keys and storage roots are now supported, allowing async to run on Aspera Files and for other Node v4 applications.
  • The new recursive mtime option enables the exclusion of directories and files older than a configured timestamp.
  • A new asyncadmin option prints file attributes (mtime, recursive mtime for directories, and checksum).
  • Pending file bytes are now reported correctly in Aspera Console during an async pull (fixed in Enterprise Server 3.6.2).
  • The new --delete-delay option allows the delete operations in a unidirectional sync to be delayed until the end of the synchronization.
  • When authenticating through Aspera Shares, asperasync.exe now passes a Shares user account in the session tags, allowing for reporting by Shares user in Aspera Console.

Cloud Support

  • HDFS and Cleversafe object storage are now supported.
  • NetApp object storage is now supported using its S3-compatible API. Browsing requires the new non-hierarchical trapd option.
  • trapd can now connect to Swift cloud storage using a self-signed certificate by setting the httpclient.ssl.cert property in /opt/aspera/etc/trapd/ to the path of the identity server certificate.


If you are upgrading from a previous release, the following changes for this release may require you to adjust your workflow, configuration, or usage.

  • With the implementation of new inline validation options, existing users with inline validation enabled must set the validation provider to uri or lua_script. The command is the same regardless of platform, but for Linux you must preface the command with its path: /opt/aspera/sbin/asconfigurator.
    > asconfigurator -x "set_node_data;validation_threshold,uri"
  • On Windows machines, the Replace a process level token local security setting must be enabled for asperarund, asperawatchd, and asperawatchfolderd to properly function. For instructions on how to enable this setting, see
  • When upgrading to 3.7.1, if asperawatchd or asperawatchfolderd services are being run by users other than root on Linux or svcAspera on Windows, the services must be stopped prior to upgrade and restarted manually following the upgrade. Services run by root and svcAspera are migrated automatically during installation.

    Run the following commands for each user and service, as required. The commands are the same regardless of platform, but for Linux, preface the command with its path, for example: /opt/aspera/sbin/asperawatchd.

    > asperawatchd --user username
    > asperawatchfolderd --user username
  • In Watchfolders, the Node API transfer account must have access control set to admin in order to create watchfolders. To update an existing Node API transfer account, run the following command. The command is the same regardless of platform, but for Linux, preface the command with its path, for example: /opt/aspera/bin/asnodeadmin.
    > asnodeadmin -mu username --acl-set "admin,impersonation"

    To create a new Node API transfer account with the correct access control, run the following command:

    > asnodeadmin -a -u username -p passwd -x transfer_user --acl-set "admin,impersonation"
  • The way asperawatchfolderd uses docroots has changed in two ways:
    1. If no docroot and no restrictions are specified in aspera.conf, asperawatchfolderd will reject the creation of a watchfolder and return an error message similar to the following:
      ERR [Watch_folderd] Handle_create(): [err=28672, message=No docroot]

      Workaround: Specify a docroot or restrictions for the watchfolder.

    2. If the docroot of an existing instance of watchfolderd changes and asperawatchfolderd later restarts and tries to reload the watchfolderd, an error message similar to the following is returned:
      ERR [Watch_folder_pool] Synchronize(): [err=22, message=Change in docroot detected: /home/user/test/s != /home/user/home/user/test/s]

      The watchfolder must be recreated following a change in docroot.

  • Recursive counts are now disabled by default, but must be enabled in order for Aspera Files to use this feature. Workaround: Edit the <server> section in aspera.conf such that <files_recursive_counts_workers> is set to 5:
  • Multi-session (parallel) transfers from 3.5 clients are no longer compatible with 3.6 and newer servers. This is due to a change in how files are split and how the splitting of individual files is configured on both versions. Workaround: Upgrade the client side to 3.6 or newer.


Note: This release contains tickets created from different tracking systems. For this reason, the ticket IDs may reflect different numbering formats.

Watchfolder and Watch Service documentation is now correct, with a description of rund, the new service that manages these daemons.

ATT-105 - In Enterprise Server 3.6.2, a confusing error message is returned when a node connection fails due to incorrect HTTP proxy credentials.

ATT-93 - ascp fails to open log directories with a "." in their filepath, for example C:\Temp\.\Logs.

ATT-92 - ascp with a forward proxy logs the DNAT proxy password when called through the command line.

ATT-72 - ascp transfers from Windows to Linux fail when the destination path includes special characters (for example, & ^ *_ ) and exceeds 520 characters.

ES-27 - In Enterprise Server 3.6.2, the transfer progress bar is absent.

WAT-331 - In Enterprise Server 3.6.2, when calls to the Node API are not returned, async hangs and does not synchronize until the service is restarted.

WAT-234 - In Watchfolder, alternate aspera.conf files are not passed to ascp.

WAT-202 - [Windows] Watchfolder is impaired after a restart when the docroot is added prior to watchfolder creation.

WAT-201 - Watchfolder counters do not persist after the source machine is rebooted.

WAT-130 - When a file is skipped or deleted, the counters on the drop and Watchfolder are not updated.

#36373 (ATT-76) - In cases of a failed transfer, the files counter in session statistics is not updated with the data for skipped files.

#36276 (ATT-79) - When the <ignore_skipped_files> setting is enabled (true) on the ES node, Console continues to show all skipped files for failed transfers on the Activity page.

#32934 - Some HTTP fallback transfers may appear to complete but then lose connection with the server and subsequently attempt to retransfer. This behavior has been observed only when the client system has an installation of the Internet accountability software Covenant Eyes, which captures the entire HTTP transmission before forwarding it to the server. If the file is large enough that this process takes longer than about 20 seconds, the server generates an inactivity timeout and cancels the session. Workaround: Reduce the probability of timeout by increasing the timeout length. This can be done by changing the Session Activity Timeout value in the HTTP Fallback tab in the server's configuration settings, or by using the asconfigurator settings, for example:
asconfigurator -x "http_server;session_activity_timeout,1200"

#30365 (WAT-286) - In the Sync Job Detail page for pull operations, the size for pending files is reported as 0 Bytes. (Transfer sizes are reported correctly after the transfer completes.)

#29172 - When using --file-list or --file-pair-list with SoftLayer, some files may not be transferred. Note: This issue is due to a defect in Swift 1.12. Correcting it depends on its correction in Swift and the Swift upgrade on SoftLayer.

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

#29305 - ascp stalls for failed file open.

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

#28686 - File-splitting only works with S3.

#28543 - ascp fails if multiple authentication methods are enabled in sshd.

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

#23246 (ATT-95) - Error messages are not generated for skipped files when using a source base setting (--src-base).


Windows:  2008r2, 2012r2, 7, 8, 10
Browsers: Microsoft Edge, Firefox 27-48, Chrome 32-50

Linux 64-bit and 32-bit: Ubuntu 12-15, RHEL 6-7, CentOS 6-7, SLES 11-12 Kernel 2.4 or higher and libc version GLIB 2.3.4+, Debian 6-7, Fedora 16-20
Browsers (for Connect Server clients): Firefox 27-48, Google Chrome 32-50


Enterprise/Connect Server

Linux 64-bit (deb): aspera-entsrv-
md5: bb3a2ffc9e00b77d531b8d49a92011af
sha1: 769d58982a0979c3f8b9ef2280304782bd6bf018
Linux 64-bit (rpm): aspera-entsrv-
md5: d6b682ef52ab95161407228ddcafc884
sha1: 32a0019adbf42680aa29a879c12f87109a56a8f1
Windows: AsperaEnterpriseServer-ML-
md5: 083a8fdfb83f32dda7e6dfb93ee79077
sha1: 533fb1b04e1ff5a79122b7856cb3b59cfe5069d8


Linux 64-bit (deb): aspera-scp-p2p-
md5: 0f0ce1da9058b60091800e9ea9513a75
sha1: 98fb82fecb579172ccbeadafd7fa25b44cd07c9f
Linux 64-bit (rpm): aspera-scp-p2p-
md5: 6c29f2b823e834af183dffa29fc1b538
sha1: 26dc2f592bee693910e945a8d37c123504a86ebc
Windows: AsperaP2P-ML-
md5: 582c3dd194267f5f1277ff3e28bd4ff9
sha1: 464081e27fa4c9fc83e37244c253a24efe6550da


Linux 64-bit (deb): aspera-scp-client-
md5: 03b4f1a0ec30375f9786c2e088f432b1
sha1: 870f4c8afc5acc016b5e158f0d174dc28959eaf7
Linux 64-bit (rpm): aspera-scp-client-
md5: 24969d536a8af3691847e42b9c68a8f0
sha1: 4f5a80222ac4e315e9433a448788fcac2e9e1488
Windows: AsperaClient-ML-
md5: 39e6714b8d9c95f774e72f9ae897befd
sha1: cf864e6d97e81a44d9995e0082c26e46bba9cc19


Note: This release contains tickets created from different tracking systems. For this reason, the ticket IDs may reflect different numbering formats.

ATT-174 - ascp fails to download and decrypt files that were uploaded and encrypted using HTTP fallback.

ATT-114 - [Windows] When a4 transfers are stopped from the remote-side GUI, files continue to transfer for some time.

ATT-96 - Transfer may fail while downloading Faspex packages if the server is configured with server-side encryption and the client is using encryption-at-rest.

ATT-31 - a4 crashes following the transfer of a large (for example, 5 GB) file to s3 storage.

ATT-30 and ATT-46 - a4 transfer is slow when uploading many small files (for example, 1 million 4 byte files) to s3 storage.

ATT-29 - Files transferred to s3 storage using a4 retain a .partial extention when viewed in the GUI.

ATT-27 - Direct-to-cloud transfers using a4 are skipped unless the full destination path is specified.

WAT-349 -aswatchfolderadmin is unable to query created watchfolders. A build of 3.7.1 is available that fixes this problem, see this knowledgebase article for more information:

WAT-278 - Watchfolder drops are lost after upgrading to 3.7.1.

WAT-174 - Watchfolder uses excessive memory when watching large numbers (for example, 10 million) files.

WAT-169 - [Watchfolder] When using top_level_dirs drop detection with x top level directories, 7(x)+ drops are created. The drop count continually increases.

WAT-152 - ascp transfers to a validation user fail with the message Session Stop (Error: Session initiation failed) if the validation provider is not set to uri or lua_script. Solution: Run the following command to set the validation provider. The command is the same regardless of platform, but for Linux you must preface the command with its path: /opt/aspera/sbin/asconfigurator.
> asconfigurator -x "set_node_data;validation_threshold,uri"

#35952 - asunprotect cannot decrypt a re-protected file.

#35857 - On CentOS7, the UI doesn't start unless there is data in the clipboard.

#35421 - Shares console becomes unresponsive during a deletion command that takes a long time to run.

#35255 - When Japanese characters that include the voiced sound mark are used to name a directory in Connect Server, the following issues may occur:
  • The upload fails without an error message.
  • The download fails with the error code 43: The specified path cannot be found.

#34811 - The user is unable to download encrypted files with an incorrect decryption passphrase when using HTTP fallback.

#34674 - When Japanese language is set on the ES UI, it doesn't respect aspera.conf settings; all docroot settings are set to false, and the other settings fail with attached Japanese errors.

#34322 - ascp fails to authenticate SHH with a large banner file size (approximately 2000 bytes) on CentOS 7.2.

#33877 - Aspera Enterprise licenses that are watchfolder-enabled don't display watchfolders as an enabled setting when running the license switch ascp -A.

#33742 - Node API /files/browse cannot retrieve the preserved modification times for ascp uploads.

#33673 (ES-18) - Transferring symbolic links on Windows results in the creation of a zero-byte file at the destination instead of the expected copying of the target of the symlink.

#33374 - The unimplemented function error does not appear when the user attempts to create a symbolic link to a file on cloud storage (S3) from the Node API. (Symbolic link capability is only available on local storage.)

#33298 - The ES Windows installer fails to install with the /quiet option.

#33229 - The client is no longer able to browse a file on cloud storage using a /files/browse API request.

#33214 - Transfers to and from cloud storage (S3)—using authorization tokens with URIs that do not have a docroot specified—are unsupported.

#33206 - /ops/transfers erroneously shows some queued transfers (which are farther down in the queue) as failed before they have completed.

#33202 - Node API allows the user to move a file in cloud storage into a directory with a /files/rename request.

#33094 - ascp delete-before-transfer does not support URI storage.

#32941 - Because pvcl does not support the --no-read --no-write option, ascp should fail transfers that use these options with pvcl. However, ascp ignores the options and continues the transfer.

#32890 - In a successful transfer from the client to the server, ascp fails to copy the metafile and thus it does not transfer with the data file.

#32680 - The option to create a directory (ascp -d) may create a directory at a destination before an expected session failure.

#32669 - When a directory is linked from a subdirectory, it does not appear in the search result for a /files/search request in the Node API.

#32627 - When a filename is just a dot and an extension, (for example, .pdf), then it is reported as a file with "content_type"=>"application/pdf" or a hidden file named PDF; for example:
{"id"=>"27", "name"=>".pdf", "size"=>12, "content_type"=>"application/pdf", "type"=>"file", "modified_time"=>"2015-09-10T15:24:01Z", "access_level"=>"edit", "permission_count"=>0}

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

#32517 - Retransfer requests are unencrypted when transfers are encrypted. This can cause transfer failures in some scenarios, such as a network device dropping the retransfer request because it detects a bit sequence it considers malicious.

#32080 - An error message spams the log file used by asperanoded each time the console attempts to check the node for the status. A second error can occur when the end user fills in a docroot but doesn't have a valid system user; this results in an error that also spams the log file used by asperanoded.

#31791 - The user is unable to transfer files with the file extension .aspx. Workaround: Edit the resume_suffix setting in the aspera.conf file on the server, and then copy aspera.conf to each source user.

#31712 - For both AWS and Softlayer Swift storage, /files returns modified_time for files but not for folders.

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

#30690 - ascp fails with an inaccurate message—Error: failed to authenticate—when a server is configured to only accept ciphers that are no longer supported.

#30542 -/files PUT (file rename) should be fixed to involve only one PVCL operation but still return the proper 409 code when there is a destination conflict, and PVCL needs to return proper error codes stating that the move operation failed because of a destination conflict.

#30324 - During an ascp upload to cloud storage, if a mid-file read failure occurs on the sending computer (which is very rare) it can cause the server-side ascp to crash and possibly fail to report transfer completion. This read failure can be caused when a source file is truncated during transfer, a drive or file system fails, or a transfer is cancelled with Ctrl+C or other means.

#30231 - [Windows] If a pre-post script includes a path that contains ".." and the client is running on Windows, ascp fails with the following message:
Cannot open -e pre-post command: Unknown error

#30082 - [Windows] When the upload of a source file to the remove server fails, no error message appears in the UI.

#29848 - When <write_allowed>, <read_allowed>, and <dir_allowed> are all set to false in aspera.conf, Node API calls to URLs such as /files/browse are returning response code 500 Internal Server Error: instead of another code that better indicates that access to the resource is denied.

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

#29613 - On Windows, the folder timestamp is not preserved when top-level directories are transferred with the -p option. (The issue does not occur when folders are created on the day of transfer.)

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

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

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

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

#29043 - Under serious WAN impairment, hotfolder push transfers with a prepost script intermittently report an assh error approximately 10-15 seconds after Transfer Statistics are reported to the log. This delay in process shutdown can hold the handle to the filelist such that subsequent ascp processes fail.

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

#28939 - If command line ascp neglects to specify a destination host, then the failed transfer (error: "no remote host specified") gets recorded in SQLite with client_node_id NULL, instead of being populated with the uuid of the node. This causes an issue with Console.

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

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

#28683 - docroot warning message: If global docroot is enabled, reports the root user as insecure.

#28679 - In some cases, the fallback server does not respond.

#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 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 by running the following command: ulimit -a | grep "open files".

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

#27823 - The user's Faspex Server goes down with an "Transfer Server errors detected" error message. An error, "trying to read events from a parser that already reported an error before" appears. Workaround: move the central-store.db to allow re-creation.

#27311 (WAT-288) - Sync: An apply-local-docroot pull copies the local docroot path into the same path. For example, /home/user1/sync is copied into /home/user1/sync.

#27056 - There is no ascmd support for server-side symlink configuration.

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

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

#26281 - At approximately 100 (or a similarly high number) of concurrent uploads to s3, intermittent transfer session failures occur.

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

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

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

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

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

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

#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 or syncing across platforms.

#25467 - async cannot be used with a cloud storage.

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

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

#25042 - In the server-side aspera.conf, the none option for file checksum reporting is no longer supported; only md5 and sha1 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".

#24918 - When shares are added to or removed from a user while the user is connected to Shares in the Enterprise Server desktop app, the remote file browser is not updated. The list of shares displayed in the remote file browser bar is not refreshed until you disconnect from Shares and reconnect to it. In the case where a share has been removed, the user will be unable to perform certain actions and it will not be clear that this occurring because the user is no longer authorized for the share.

#24805 - For a synced directory, while all of the files and subdirectories under the source folder will have ACL preserved at destination, the ACL for the source folder itself will not be replicated to the remote destination folder.

#24780 - Async: Both --preserve-acls and --remote-preserve-acls need to be specified in order for the target side of the pull to apply the acls.

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

#24390 - HTTP Fallback upload operations fails with the message "Failed to create HTTP session on server!".

#23954 - Sync: When the --preserve-acls or --preserve-xattrs option is used, async will not preserve the acl or xattr when either file acl or xattr is modified and (a) file content is unmodified or (b) file content is unmodified and the file is renamed.

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

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

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

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

#23400 - [Linux] Beginning with async 1.5, the user is permitted to sync to the root directory.

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

#23004 - Console does not draw a line between the involved nodes for an async transfer. This issue occurs when using two managed nodes with two interfaces on two different networks.

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

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

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

#22741 - When the --file-checksum feature is enabled, transferring ES 3.3.3 to ES 3.3.0, the file is corrupted at the destination with additional characters appended to the end.

#22633 - Sync does not support large xattr/ResourceForks.

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

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

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

#21978 - [Linux] ES is unable to view logs as superuser unless a functional browser is installed.

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

#20767 - Sync: -R log dir creation from Linux to Windows with spaces in the path will only get as far as the first space in the path.

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

#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 the root, 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 database 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.

#18368 - Files with a backslash in the filename are not displayed in the list when the user browses the remote source on the new package page.

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

#17231 - On Linux, an async pull does not restore access time on the source side.

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


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