Enterprise Server 2.5.0 Release Notes

Enterprise Server 2.5.0 Release Notes
for Enterprise Server, Point-to-Point, Client, and Connect Server
Version 2.5.0
Platform: Windows, Mac, Linux
Created: September 4, 2009
Last Updated: September 25, 2009 
What's New
  1. A brand new look and feel for Aspera Enterprise Server user interface.
    • The ability to execute multiple transfers at one time
    • The ability to queue transfers
    • The ability to monitor server transfers and hot folders
    • Server configuration can now be done through the user interface
  2. Improvements to Connect Server
    • Easier to make customizations
    • A new consolidated directory for customizations
  3. Improvements to the Windows installation
    • Simplified upgrade process from 2.X to 2.5
    • All services can be run under the svcAspera service account or other domain account.
    • Separate product specific directories.
    • A new simplified directory structure.
  4. A new license system
  5. A new consolidated directory for pre- and post-processing customizations
  6. Console Support - support for private/public key authentication for console initiated transfers 
  7. Transfer Features - simplified transfer policy (now using fixed, high, fair, and low transfer policies)
  8. Support for openssh private/public keys (in addition to supporting ppk keys)
  9. Support for Mac OS X 10.6 Snow Leopard 
Fixed Issues

This list covers the critical and major problems fixed in Enterprise Server 2.5.0.

  1. ascp
    • Fixed pattern matching for excluded files where files specified on the command line that should be excluded are now properly excluded. (#3156)
    • Public key authentication is now supported in Windows Vista. (#912)
    • Fixed issue when symbolic links are skipped, ascp incorrectly reports the excluded files in its pre-transfer count of files to be transferred. (#2671)
  2. Connect Server ("Aspera Web")
    • In the Connect Server, attempting to delete an empty directory without permissions no longer fails silently. (#2592)
  3. Console/faspexSupport
    • In faspex 1.6, fixed problem which prevents Windows user manager from adding/removing users.
  4. Others
    • When upgrading your product from a prior release, the existing SSH Host Keys are now preserved.
Known Issues

This list covers the known problems with Enterprise Server 2.5.0:

  1. The function to "Automatically delete source files after transfer" in 2.5 is not compatible with 2.0.2. When the client side running 2.5 initiates a download from the server running 2.0.2 with the "RemoveAfterTransfer=yes" option the source file will not be removed after the download completes and there is no error message displayed.
  2. Application freezes when changing from Windows Class to XP style and vice-versa. Workaround: Close the application prior to changing the desktop theme. (#3009) – Version 2.6
  3. Cannot chdir into a local directory that has UTF-8 characters on Windows 2008. (#3597) – Version 2.5.1
  4. Changes to global limits (vlinks) don’t get applied to active transfers. (#4363) – Version 2.6.0
  5. IIS 7 is not natively supported. To install Connect Server to IIS 7, the IIS 6 Compatibility Components is required to be installed. For instructions, go to http://technet.microsoft.com/en-us/library/bb397374.aspx.
  6. Public keys created with Enterprise Server 2.2.1 on Windows Vista or 2008 are not detected by 2.5.0. Workaround: Copy the keys from your appdata roaming directory, ie. C:\user\administrator\appdata\roaming\microsoft\windows\.ssh, to your home directory, ie. C:\user\administrator\.ssh. (#5079)
  7. A typical installation of Enterprise Server 2.5.0 on a Windows server with an existing Cygwin installation is not fully-supported without additional steps.  Workaround:  Do a custom installation without installing SSH Server and use a third-party SSH Server or contact Customer Support for details on the additional steps. (#4822)
  8. After updating the destination of a Hot Folder, the updated destination is not reflected in the Hot Folder Control Panel until that Hot Folder runs a first time.  (#5099)
  9. Due to a bug in the Enterprise Server 2.2.1.17909 through 2.2.118906 MSI packages, the upgrade to Enterprise Server 2.5 may fail if the current installation does not have the default SSH server running. Workaround:  Follow this link for instructions to remove the previous package before installing Enterprise Server 2.5.
  10. If there are more than 15,000 transfer records in the transfer panel, asperascp.exe may run out of memory. Workaround:  Close the application or delete transfer records periodically prior to hitting the upper bound. (#5084)
  11. The Docroot configuration setting, Browse Allowed, is not supported.  The setting should always be set as "true" otherwise there may be unexpected issues. (#5126)
  12. If a group entry is deleted, the user's inherited settings will not reflect the change until the Server Configuration window is closed.  All changes are reflected in aspera.conf as expected. (#5118)
  13. If <WEB> section has a rate specified in percentages (for example 75p).
    Workaround: modify the v1 conf to use an absolute rate, for example 45000 or 100000 and re-run the conversion tool.
  14. Hybrid v2 conf files are not converted (intentionally). These are the conf files used in 2.1 for HTTP fallback. We introduced a hybrid system before the v2 conf file was ready, because http uses it for its configuration. (#3522)
    Workaround: remove the version="2" from the top of the file, then convert manually, then visually inspect the configuration file to make sure it captures both the old v1 directives as well as the v2 ones.
  15. faspex 1.5 prevents Windows user manager from adding/removing users.  This happens because faspex holds the passwd file open. This is fixed in faspex 1.6.
  16. Windows permission problems for passwd or group file. This causes the user manager to fail silently.
    Workaround: fix file permissions to allow the account operating the user manager or conversion tool to write the files.
  17. User accounts that no longer exist. The conversion will not be able to find the user name for all the UIDs in the old docroot file. It will add the users in aspera.conf by using their UIDs (for example 1111, 1112).
    Workaround: either create the users that are still needed, or delete them from the docroot file before the conversion.
  18. Transfers may fail if the following characters are used in the source or destination file names: (/ \ " : ? > < & * |).(#3431, #3453)
  • ascp strips beginning of path if path contains a colon (:). Workaround: Avoid using the colon in the folder and the file name.
  • In the Connect Server, the question mark in the source file name prevents the transfer. Workaround: Download the containing folder or rename/move the file. (#3476)
  • In the GUI, trying to delete a file with the " (double-quote) from the local computer results in silent failure; trying to delete a file with the " (double-quote) from the remote server results in the error message: "Invalid command or token separator mismatch" Workaround: Delete or rename the file via OS provided mechanism, such as the file explorer and the Finder. (#3451)
  • In the user interface, the transfer fails when the back-slash (\) is used in the file name. Workaround: Avoid using the back-slash in the file name. (#3452)
  1. If you are upgrading from version 2.1.3, the configuration file aspera.conf will not be converted into the new format. Refer to the product's user guide for manual configuration instructions. (#3522)
  2. In the log file, if the peer is running Aspera's product prior to version 2.1.2, it displays x.x.x.x. (#3497) - Won't fix
  3. If a file is dated earlier than January 1, 1970, ascp crashes on a _localtime64 assert. (#2421)
  4. When an exclude filter is used, ascp incorrectly reports the excluded files in its pre-transfer count of files to be transferred. (#3157)
  5. When transferring a single file to a non-existing target directory, using the -d option to create the directory, the directory creation fails to respect the permission settings specified in the aspera.conf. (#2802)
  6. If the default policy is set to "trickle" or "low", Connect Server will use "fair" as the default policy. (#4575)
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk