Enterprise Server 2.6.1 Release Notes

Enterprise Server 2.6.1 Release Notes
For Enterprise Server, Point-to-Point, Client, and Connect Server
Platform: Windows, Mac, Linux, Solaris
Version 2.6.1
Created: April 7, 2010
Updated: May 10, 2010

 What's New

  • Brand new graphical user interface for Linux

  • Rule-based virtual link setting (For CS, ES, and P2P only)

  • Apply aggregate bandwidth policies to transfer groups by IP address or metadata

  • FIPS 140-2 compliance

  • Native IPv6 support

  • fasp v2.6

    • Persistent transfer session for on-the-fly additions to transfers

    • Configure vLinks by transfer properties (e.g. by peer IP address and or user-specified cookie)

    • Independent source and destination naming

    • Reverse path congestion control (default: ON). On top of existing adaptive rate control, it handles situations where congestion happens on the reverse transfer path. It particularly boosts the performance of ascp for bi-directional transfers on links with asymmetric bandwidth (e.g., ADSL)

    • Optimal performance extended to network conditions with heavy out-of-order packet delivery scenarios

    • Various fixes

  • Many updates to the user interface, including

    • Configurable email notifications

    • Password confirmation for the encryption and decryption settings

  • Support for Windows UAC

  • Newly redesigned documentation with search support

  • Connect Server update

    • Three new configuration settings have been added: dir_allowed, read_allowed, and write_allowed

  • Windows integration with Cygwin 1.7.1-1 final release

  • On non-Windows or Mac OS X platforms, any references to Aspera binaries in /bin have been removed except for aspshell.  Please begin to reference binaries from /usr/bin only as all references from /bin will be removed in a future release.

Fixed Issues

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

  1. Aspera User Interface

    • Fix SSH key creation if the SSH Server feature is not installed or running Client. (#5718) 

    • Fix issue with missing file exclude setting under Configuration -> Advanced File Handling (#5119)

    • Fix problem with the sharing option always being greyed out when creating a new Connection on Mac OS X. (#5230)

    • Fix problem where the GUI doesn't display a Kanji username on a Japanese version of Windows. (#5638)

    • Fix issues when logging in with a user account with unicode characters (#4884)

    • Refresh local file view after a transfer completes. (#5451)

    • 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)  

    • Fix issue where the transfer status remained as "Stopping" even though the transfer is continuing. (#4743)

  2. Hot Folders

    • Fix Hot Folder sync failure when transfers run from Saturday into Sunday. (#5759)

    • Fix issue when one user creates a Hot Folder and exits then another user launches the GUI and receives an error about reading the hot folder configuration. (#6146)

  3. Connect Server

    • Fix download failure from Mac OS X server when using HTTP fallback. (#5195)

    • Docroot path no longer has to be case sensitive on Windows XP (#1633)

    • Fix Connect Server to support unicode characters in the docroot path. (#3096)

    • Fix error message to accurately display if a file cannot be deleted. (#5710)

    • Fix Connect Server to validate PathMTU value setting in aspera.conf. (#5012)

  4. Central

    • Fix Central for Windows to run with the -DDD debug arguments from the Services panel (#5850)

  5. Console/faspex Support

    • Fix session details page in Console to display the correct values when HTTP fallback is enabled (#2267)

    • Fix Directory Create Grant Mask error in Console. (#5659)

    • Fix Console SmartTransfer job requests for new users from failing on the first attempt. (#5985)

  6. fasp

    • Update license output from ascp to reflect the license type (#5425)

    • Fix problem where fasp didn't print the product info into the logs. (#4459)

    • Fix problem with ascp hanging when transferring to a non-existent destination path with file manifest enabled. (#5293)

    • Fix failed transfers when the the transfer path has unicode characters on Mac OS X when the language is set to Chinese. (#5530)

    • Fix ascp download failure when the destination is a drive letter without ending slash (#5767)

  7. Other

    • Fix problem with aspera-notif.pl not running on Mac OS X due to ^M characters. (#4444)

    • Update aspera-prepost.disable with the correct RATEMODE and SECURE values (#3229)

    • Fix problem where the the HTTP fallback transfer uses ownership credentials of asperahttpd, not the transfer user. (#5434)


Known Issues

  • On Linux, previewing the email template may return an error message if your default browser is Firefox v1.5 to v2.x.  Workaround: Uninstall the older version of Firefox.  Install Firefox v3.x and make sure that when typing 'firefox' from the command line, v3.x is opened. (#6108)

  • In the Windows graphical user interface, files with foreign language characters in the filename or path cannot be decrypted.  Workaround: To decrypt the file:  1st, rename the file to English.  2nd, move the file to a directory without any foreign language characters or rename the directory to English. 3rd, proceed with decryption.  Or an alternative method is to download the file with the "Decrypt password-protected files downloaded" option selected located under Connection Manager -> <Your connection> -> Security. (#6511)

  • When your regional and language options are set to a language standards and formats that doesn't use "." to represent the decimal point, values are displayed inconsistently using both "." and the native character to represent the decimal point. (#6448)

  • In situations where a user is a member of multiple groups and a value from an inherited group changes, the value will not be displayed correctly.  The actual user experience will be as expected. (#6473)

  • In Windows, while a Hot Folder is running, editing the source path for this Hot Folder, then saving and clicking the "Refresh" button may cause Sync process to hang. If this occurs, restart the Asperasync service. (#6457)

  • In the Windows graphical user interface (GUI), Preferences settings are properly reflected in aspera.conf, but not reflected in the GUI's Configuration until restarting the GUI.  (#6453) 

  • When connecting to a connection through the Windows graphical user interface (GUI), clicking on the "Cancel" button may not always stop the connection from being made.  In this case, disconnect from the connection after it has been established. (#6449)

  • A new Hot Folder is lost if two administrative users have the Windows graphical user interface (GUI) open, if administrator #1 creates the new Hot Folder and exits the GUI then administrator #2 closes the GUI, the result is the new Hot Folder that administrator #1 created will be lost. (#6443)

  • Periodic SSH connection failures on Windows 7 32-bit such as the following (#6341)

Session Stop (Error: Session initiation failed, SSH connection failure: Server cannot invoke command; is it installed?) 
Session Stop (Error: SSH connection failure: Server refused to start a shell/command) 

Session Stop (Error: SSH connection failure: Connection reset by peer)
Workaround: Use Windows 7 64-bit.

  • Connect Server on Windows does not allow unicode user names. (#6302)

  • On Windows, Hot Folders do not work when the user has unicode characters in the name.  The transfer fails with the status "Authentication failure." Workaround: Setup the Hot Folder with user credentials in English (non-unicode) characters.

  • Ascp cannot be invoked with a comma in the path. (#5210)

  • dblogger may fail to initialize mysql on some distributions of Linux (i.e. Fedora 8 and RedHat 5).  Workaround:  Change the security settings from "enforcing" to "permissive" or "disabled."  Or change the module security setting with "chcon -t" to execute the following command: chcon -t textrel_shlib_t /opt/aspera/lib/db/libasmysql.so (#3230)

  • The Connection detail information may be incorrect after clicking "OK" on the "Share Private Key?" dialog.  Workaround:  Close and reopen the dialog to view the correct information. (#6547)

  • Connect Auto-Installation

    • On Windows, a non-administrator will not be able to uninstall Connect if it was installed via the applet installer and another user installed Connect via the applet installer and Connect is running. (#5600) Workaround: Notify the other user to close all browsers and Connect processes before running uninstallation.

    • On Mac OS, during a Connect upgrade via the applet installer, the installation location is changed to ~/Library/Application Support/Aspera/Aspera Connect.  (#5652)

    • On Mac OS, if Connect 2.3.0 was installed by an administrator account, a non-administrator will not be able to upgrade to 2.3.1.  The upgrade does not report any error, but Connect 2.3.0 will still be installed. (#5662)  Workaround:  Notify the administrator user to upgrade to Connect 2.3.1.

  • Browsing a directory containing over 250,000 files may cause the Mac-Intel SCP GUI to hang. (#5442)

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

  • Application freezes when changing from Windows Class to XP style and vice-versa. Workaround: Close the application prior to changing the desktop theme. (#3009)

  • Changes to global limits (vlinks) don’t get applied to active transfers.

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

  • 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)

  • 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)

  • Due to a bug in the Enterprise Server 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.

  • 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)

  • The Docroot configuration setting, Browse Allowed, is not supported.  The setting should always be set as "true" otherwise there may be unexpected issues. (#5126)

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

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

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

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

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

  • 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)

  • 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)

  • 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)

  • If a file is dated earlier than January 1, 1970, ascp crashes on a _localtime64 assert. (#2421)

  • When an exclude filter is used, ascp incorrectly reports the excluded files in its pre-transfer count of files to be transferred. (#3157)

  • 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)

  • If the default policy is set to "trickle" or "low", Connect Server will use "fair" as the default policy. (#4575)

Package Information

MD5 Value: 

D68F5C5EA6EBB336F086B67030E6400C  aspera-entsrv-
968D8F4BB8531737921B9975F14B7768  aspera-entsrv-
8A61D04DDDF1A3EE25E9F53662896B40  aspera-entsrv-
8BFCABF4C6F0A3BF10E6FB461D40C619  aspera-entsrv-
B39AAFA6D557AA6AF6784B4500B4FE35  aspera-scp-client-
624C2DFC4D59BDC982016D50705E88A2  aspera-scp-client-
B5ADDE734510370FC2F16278F2C68DB9  aspera-scp-client-
D1FFE9850FFC662A43A92B6F17BB9266  aspera-scp-client-
9C12E4332735586CBF17928E4AC663F5  aspera-scp-p2p-
1C4D00DAB00811A8FDA6E4C5FB140C75  aspera-scp-p2p-
D364B68B093DB1695747FC1586F862F6  aspera-scp-p2p-
9B9FBE80930657F9EAFAB18E37AE5774  aspera-scp-p2p-
B9068C9671786E1198F2982ACBD1CA16  AsperaClient-
7B446B9BBCB36B0ED35C258EA663B7E2  AsperaClient-
2B9F89CB884C06D0B818C7242EF05F7A  AsperaEnterpriseServer-
50AF435C8B7430AF064E3942096B4C21  AsperaEnterpriseServer-
E84F8F4FA1C53BE93B97191D50EDE09B  AsperaP2P-
BD5D701DA12A269C95BE15E80EF3FEBD  AsperaPointToPoint-
3441BFCFA4B7F816DBDF623568F2DE50  aspera-entsrv-
52453F0210D93FB76206A3AC80A5A829  aspera-scp-client-
58792EFF10545D18D30E394BB4D36555  aspera-scp-p2p-

Powered by Zendesk