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

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

Product Release: Jan 22, 2016
Release Notes Update: Jan 22, 2016


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

New Features

  • Support for the following new Aspera product releases: Aspera Files 1.0.0, Shares 1.9.3, Console 3.0.3, Connect 3.6.2, and Aspera On-Demand 3.6.0 (for AWS, Azure, and SoftLayer), and ATCM 1.0.0 (Aspera Transfer Cluster Manager).
  • Aspera introduces access key authentication for Ascp and Async. Access keys provide an alternative to the security credentials of a node user or system user. Because an access key is restricted to its own storage (local or cloud), it allows access control and usage reporting to be segregated by storage. This offers significant benefits to multi-tenant service providers and enterprise installations with multiple departments. Access key authentication supports Aspera client products, such as Desktop Client, Point-to-Point Client, Enterprise Server, Connect, and Drive. It also supports Faspex, Shares, and Aspera Files. For details, see your product documentation for these products.
  • A new Aspera Watch service (asperawatchd) provides ultra-fast file-system change detection and a snapshot service for speed, scale, and distributed sources. The watch service discovers changes in source file systems (new files, new directories, deleted items, renamed items, and so on) immediately as they occur, eliminating the need for scanning the file system. It can be used on any local host or shares host (CIFS, NFS). The watch service integrates with the following:
    • Async for fast synchronization of large numbers of files without scanning.
    • Ascp for fast detection and sending new and deleted items.
    • The new Aspera Watchfolder feature for a fast, scalable watchfolder.
  • A new watchfolder feature automates file transfers from a source to a destination system. Files placed into a designated source folder are automatically transferred to the destination. Watchfolder transfers are run from the source machine only and do not require any additional software on the destination system.
  • Server-side encryption-at-rest (EAR): EAR encryption and decryption can now be done from the server. The passphrase is set in aspera.conf. Client-side EAR is still available as before.
  • The ascp command has new options for preserving OS X extended attributes (xattrs) and Windows Access Control Lists (ACLs), regardless of the type of file system storage: --preserve-xattrs, --remote-preserve-xattrs, --preserve-acls, --remote-preserve-acls.
  • The ascp command has four new options for preserving timestamps: --preserve-creation-time, --preserve-modification-time, --preserve-access-time, and --preserve-source-access-time.
  • Async now preserves POSIX attributes in the event that file attributes change but file contents do not (times, UID, GID).
  • A new ascp option, --remove-empty-source-directory, removes the root source directory after a transfer. This option is a companion to --remove-empty-directories, which deletes subdirectories but not the root source directory.
  • Users can now run asnodeadmin --db-update to migrate data from Enterprise Server 3.5.6 and earlier versions.
  • Node API transfer jobs can be split into multiple ascp sessions to take advantage of multiple computers or multiple cores and I/O streams on a single computer. This is governed by two parameters: (1) the ascp option -C, which enables multi-session transfers (also known as parallel transfers) and specifies how many sessions to run per job, and (2) a new ascp option --multi-session-threshold=threshold which specifies whether to split large files equally between sessions, or have each session transfer full files. For cloud storage, file-splitting is currently supported for S3 only. For details, see Ascp Command Reference in the Enterprise Server 3.6.0 Admin Guide.
  • Aspera Sync: When using the --keep-dir-local or --keep-dir-remote options, locating the keep-dir under the same directory as the sync directory is no longer an error condition as long as the keep-dir has been added to the exclude list.
  • A new asnodeadmin option --show-job-queue allows the node admin to view the current queue of transfers.
  • A new asnodeadmin option --show-transfer-log allows the node admin to view all transfers (ongoing, completed, failed, orphaned, and so on), except for those currently in the transfer job queue.
  • Folders created in s3Fox (Firefox plugin directory) will display with the conventional directory name structure (filename/) in the Enterprise Server UI when the following file is edited to set the following property to true: = true.

    If the default property ( = false) is not edited, the directory name displays as filename_$folder$ when the user restarts Trapd and browses to the folder in the UI.

  • A new option Delete empty source subdirectories has been added to Connection Manager > File Handling. This option is used in conjunction with the options for moving or deleting source files after transfer, neither of which moved or deleted source subdirectories. Note that this option does not remove the root source directory.
  • Users are now able to set a policy for retrying node-to-node transfers. These options are set in aspera.conf and the node API.
  • File links are now supported for cloud storage. The "links" are small text files have the following naming convention:
    Limitations: The current implementation (of uploads) does not check whether a file with a -lnk name already exists at the destination, and pvcl_trap does not handle the symlink type, hence the "symbolic link" symbol is not displayed in the UI.
  • Ascp has a new option, --delete-before-transfer, for deleting extraneous files at the transfer destination. Files that are "extraneous" are those that exist at the destination, but not at the source. A new utility asdelete provides the same capability from the command line.
  • On the DBLogger, options for the persistent store (ignore_empty_files, ignore_no_transfer_files, ignore_skipped_files, and file_errors) are configurable in aspera.conf.
  • Async: A new option (--scan-interval) allows the user to run a periodic scan in async. This new option takes a time spec.
  • Java SNI support is now available for HTTPS requests.
  • License support is now available for multiple entitlements per computer.
  • It is now possible to preserve the UID, GID, and timestamps to the Aspera Central SOAP API with a job order.
  • Source files can now be deleted after transfer using the --remove-after-transfer option with ascp or async, or from the desktop UI (Connections > File Handling > Automatically delete source files after transfer). This feature does not remove directories.
  • It is now possible to bind asperanoded to a specific address.
  • Users can now include customizable fields in the subject line of transfer notification templates.
  • Added support for storage to blob pages in Azure.
  • A new feature -- configurable in aspera.conf -- allows a user to request that unsupported Windows characters in filenames and path names be converted to a user-specified Windows-safe character. If this option is not enabled, uploading or downloading a filename that contains an illegal character generates an error.
  • Docroots can now be configured using $(home) for a user's home directory. This is also supported by asconfigurator.
  • Users can now specify token lifetime using *_setup in the node API. Previously this was only possible using an astokengen option.
  • The response to an ops transfer get request now includes job_state in the list of transfer sessions.
  • The save-before-overwrite feature no longer requires the sending or receiving client to use --partial-file-suffix.

Breaking Changes

  • async -t no longer preserves access times (only modification times and on Windows, creation times).
  • If a node has <preserve_times> set in aspera.conf, Faspex 3.6.2 and older will break. However, Faspex will not break if <preserve_attributes> is any which is the default.
  • ES on OS X 10.11 (El Capitan) breaks SSH services due to System Integrity Protection. Workaround:
    1. Add the following to /etc/ssh/sshd_config:
      PermitUserEnvironment yes
    2. Restart sshd:
      $ sudo launchctl unload /System/Library/LaunchDaemons/ssh.plist
      $ sudo launchctl load  /System/Library/LaunchDaemons/ssh.plist
    3. Under .ssh/environment, set the path to the Aspera binaries:
      # /Users/$USER/.ssh/environment
  • Ascp transfers now fail with an "invalid authentication" error when an invalid token is supplied.
  • Node API /transfers is deprecated and has changed (and job_id field is no longer present in response).


$34166 - Memory leaks in asperanoded result in customer crashes.

#34036 - Connect Server does not work with docroots set in the URI format file:/// in aspera.conf.

#33975 - Console transfers that use SSH keys no longer work after upgrading to 3.6.0.

#33768 - Enterprise Server 3.6.0 (for Linux) + Faspex 3.9.3: For transfers of packages with symlinked files, the referenced file path replaces the docroot with "/". For example: Your docroot is /home/aspera/packages; in your package, you send /home/aspera/packages/testfile1; the resulting symlinked file points to /testfile1. As a result, Faspex is not able to find the file when it attempts to download it.

#33635, #33626 - (Windows) When upgrading from 3.5.6 to 3.6.0, the hot folder file list directory name conflicts with the legacy file list name, causing hot folders to fail.

#33609 - Submitting transfers from multiple access keys and querying GET /transfers exposes data from all tenants on the node, including passwords encoded in basic tokens.

#33567 - HTTP fallback uploads fail when the docroot is configured with file:/// (three slashes).

#33250 - When ASPERA_LOCAL_ACCESS_KEY is set with a fake entitlement, transfers are prevented only intermittently.

#32805 - async truncates paths to 100 characters for faspmgmt.

#32538 - Sometimes Google storage fails to finalize multipart transfers with HTTP-429 during the compose operation.

#32310 - In a cluster environment, Node API fails to start with the error message, "conflicting schema version".

#32225 - Calling as_volume_info in ascp to return the volume size of a UNC path on a node returns an incorrect value (volume size of the local drive).

#31858 - Packages with title names that contain an ellipsis ("...") cannot be deleted.

#31643 - Absolute symlinks are not copied but report a successful transfer.

#31628 - When ascp file validation is enabled and the destination path is very long, the POST request to the file validation server does not contain the filename; instead, it contains a number.

#31226 - When both encryption at rest and HTTP Fallback are used, uploaded files become folders containing the file, .aspera-env.

#30592 - The async candidate in progress counter needs to be reset for a new scan session; the counter increments but doesn't decrement or clear on restart. This seems to occur when the user cancels async while a sync is in progress.

#30301 - On certain Windows 2012 server hosts, the asperacentral process stops all network activity and logging to its flat file log.

#30262 - Non-UTF 8 characters appear in the central database (from HTTP Fallback).

#30131 - Asperacentral server script status does not work in RedHat 7.

#29704 - An authentication error is received over Google Storage after a machine reboot (authentication is refused with an empty key).

#29585 - Users who don't have download access and try to connect with a GUI get an "internal server error".

#29305 - ascp stalls for failed file open.

#29239 - There is no support for use of the "&" character in usernames for hot folders. If it is entered in the sync.conf, the user sees an error message every time the file is accessed.

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

#29145 - ascp bandwidth measurement is not printing to stderr on the local client.

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

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

#27822 - The user's Faspex server goes down with the error message "Transfer Server errors detected". The error listed in the UI is: "trying to read events from a parser that already reported an error".

#27639 - A user's groups can't be seen on a Linux system using AD integration when the group names are long. If any name in the list is long, all groups are either not seen or ignored.

#27147 - On Mac OS, getting metadata from a filename that begins with "._" generates an error.

#25487 - Aspera Central crashes when subscription observer service is registered.

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

#12854 - Currently Trapd uses data chunks of ~64 MB and the AWS API allows 10000 of these chunks, which therefore limits the uploaded size to 625 GB instead of the 5 TB allowed by AWS.

#12402 - does not distinguish correctly between insecure and secure users.

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


Windows:  2008r2, 2012, 7, 8, 10
Browsers: Internet Explorer 8+, Firefox 27+, Chrome 32+

Mac OS X: 10.7 and higher

Linux 64-bit and 32-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+.
Browsers: Firefox 27+

Legacy Platforms: Due to issues of security and performance on modern hardware, the following older platforms are supported in only a limited fashion: Windows XP, Windows Vista, Windows 2003, Mac OS X 10.5 and 10.6.


Enterprise/Connect Server

Linux 32-bit (deb): aspera-entsrv-
md5: a31cd0bd6949bd412fe588d9c721248f
sha1: 825aba1285e8cbe7632d1bc4c87da6f76628a97e
Linux 32-bit (rpm): aspera-entsrv-
md5: 2fe69acc4162f7119c9cf1028df6837b
sha1: 7626b0ba92388132844e3099bff4113111ba0b1b
Linux 64-bit (deb): aspera-entsrv-
md5: 36e19c2ed09fd4b6c1ac6af878eedcff
sha1: 2a357e29c0bca31353cc0a6cbbfaed7f74c0ac45
Linux 64-bit (rpm): aspera-entsrv-
md5: bf5ee817d0dca3d1ecabe533adf25fe1
sha1: 3a12c7e4f30531a2269c5f6252894f9497b795a5
Windows: AsperaEnterpriseServer-ML-
md5: 979a2e6f8649a4043b3d8f09176abce2
sha1: 7790fd15d57727cb81b7ad91670976167d33e8ae


Linux 32-bit (deb): aspera-scp-p2p-
md5: 6dda196c857df9278c8a9fbbbd46cdc2
sha1: ed4fc68d135f68775634f7a4eafc0f105323a708
Linux 32-bit (rpm): aspera-scp-p2p-
md5: 93331536c2a970d322e20dc121dea7a6
sha1: e381baa1b41b9f7e31738bcd4610e16214c99c28
Linux 64-bit (deb): aspera-scp-p2p-
md5: 51b8d510efa4251da3dd3576ceba80f2
sha1: 6c9da65983d3b85ce1130c8cb5fd1c3c85ea039a
Linux 64-bit (rpm): aspera-scp-p2p-
md5: 1b06eec12d6abf3398f6abe73199cb09
sha1: 918537bbc53b0ff380620dc36f13be5e0fec18d8
Windows: AsperaP2P-ML-
md5: c5bc628186770a98881a22131c6b0bfc
sha1: 9005264fbbf9954c62ec36eb0643f26658d44c3b


Linux 32-bit (deb): aspera-scp-client-
md5: 9ec7fd0e217d3a20b8bcb807db5208a3
sha1: ca2754e89889a4594de50dc1ac86e0d05bb3c3a3
Linux 32-bit (rpm): aspera-scp-client-
md5: a4f0f6c584883edaeb82cbd2082265f0
sha1: e3fd7f85ded5fb3862ceadc15422e17bd59b0810
Linux 64-bit (deb): aspera-scp-client-
md5: b698a98dd7bb6aa65f9d1c9f9dfe9854
sha1: e0280ed4d6ba783d4e44fa9cb65ea31b58607944
Linux 64-bit (rpm): aspera-scp-client-
md5: 868e752418eda6b6b3c1d4f1350bb689
sha1: e9f157ee2c447df6efc07e783dd44ad803a71370
Windows: AsperaClient-ML-
md5: 6edade3896c5803a4e964e0581e0a51e
sha1: b950abc19dd82bd88ddc7c8170ad293472a28dce


#34045 - Connect Server for Linux cannot be browsed from the browser when the doc root is set using file:/// .

#34031 - Setting the docroot with the file:/// syntax in the GUI results in the following error popup: Bad Settings (11) - "file:\\\C:\" is not a valid value for "Absolute Path" (Invalid characters)" Workaround: To use the file:/// syntax, set the docroot in aspera.conf.

#33198 - Console cannot connect to Windows Enterprise Server nodes through SSH.

#32941 - ascp fails transfers with the --no-read --no-write option using pvcl.

#32934 - HTTP fallback transfers appear to complete but lose the connection and Connect Server attempts to retransfer. This behavior has been observed only when there is an installation of the Internet accountability software Covenant Eyes, which intercepts and captures an entire HTTP transmission. If the file is large enough and takes more than about 20 seconds, the server generates an inactivity timeout and cancels the session. Workaround: Use asconfigurator to increase the timeouts.

#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, (for example, .pdf), then it is reported as a file with content_type "application/pdf". It could also be reported as a Unix hidden file named "PDF".

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

#32064 - async/s3, async -C stays running with one pending when moving a directory.

#31962 - Noded-initiated parallel transfers can cause file corruption.

#31791 - The user is unable to transfer files with the file extension .aspx. Workaround: Copy the aspera.conf to each source user to override the setting.

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

#31423 - An ascp transfer of a file on a full disk is reported as successful by both the sender and the receiver.

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

#31033 - On Azure, creating a file whose name ends with a "." fails. The trailing dot is discarded. On Azure, files cannot end with a "dot" or a "/".

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

#30616 - On Isilon, asconfigurator fails with "no space left on device". If this occurs, restart the server so that handles are released.

#30572 - Azure produces errors when some types of UTF-8 characters are used.

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

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

#30277 - In the GUI, when a user right-clicks a hot folder transfer intiated on another machine and then clicks Edit, nothing happens.

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

#30082 - When a Source Move destination is set in the GUI, but the source file cannot be moved, no error message is displayed.

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

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

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

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

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

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

#28686 - Multi-session uploads to S3 with file splitting must have the ascp chunk size and the S3 part size set to equal values. (File-splitting only works with S3.) File-splitting needs to respect a minimum split size, which for cloud storage is a part. That is, each ascp call needs to deliver full parts. Minimum split size is specified with the ascp option --multi-session-threshold. However, note that if the file size is greater than the multi-session threshold and smaller than the chunk size, then there is no split. Set chunk size and part size as follows:
  1. In aspera.conf set the chunk size to some value greater than 5 MB; for example:
    <chunk_size>67108864</chunk_size>   <!-- 64 MB -->
  2. In /opt/aspera/etc/trapd/
    • Set the upload part size (default 64 MB) to the same value as the chunk size.
    • Use a ONE_TO_ONE gathering policy:

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

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

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

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

#27439 - Cannot install on Fedora due to "Missing security signature". Workaround: Install from the command line only, as documented.

#27425 - Cannot install on Ubuntu using the UI. The error message states "The package is of bad quality." Workaround: Install from the command line only, as documented.

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

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

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

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

#26188 - Mac Azure: Certain Unicode characters () in the name of a folder or file will cause a transfer to fail.

#26186 - User cannot start SCP transfers with Client or P2P on Mac 10.5.

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

#26048 - In the Windows Nimbus theme, trying to select multiple files using the Control or Shift key selects only the last file clicked.

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

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

#25748 - On a Mac, when the user transfers a SAMBA directory with more than 92 files from an SMB mount, some files are omitted

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

#25467 - async can now 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 - Both --preserve-acls and --remote-preserve-acls need to be specified in order for the target side of the pull to apply the acls.

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

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

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

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

#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 - async 1.5 permits the root directory to be synced on Linux.

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

#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 - ES is unable to view logs as superuser.

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

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

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

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

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

#20347 - Sync reports errors and conflicts for deep directory depth when sync is from Linux to Windows.

#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 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 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 - An async pull does not restore access time on the source side. This behavior has been observed with Linux.

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

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

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

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

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

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

#13826, #13827, #13833 - Limited support for Unicode filenames on Windows: The user creates in a directory with a name containing unicode characters (for example, Japanese), and then creates a file in that directory. The following errors may occur:
  1. Running with an -N set to a string with non-English characters (such as Japanese) causes an error message.
  2. After performing a sync, the UI displays an inaccurate directory name and path separator.
  3. After syncing, using the asyncadmin -M option does not allow the user to delete the file from the database.

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

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

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

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

#9126 - Sync logs events at a fast rate. The log destination must have room for large log files.

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

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

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

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

#8412 - Backslashes in filenames is not supported.

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

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

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

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

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

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

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

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

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

#5527 - The application may not respond cleanly to the file system it uses becoming full. After making more room, it may be necessary to forcibly shut it down and rebuild the snapshot database before normal operation is restored.

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

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

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

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

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


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.