faspex 2.6.0 Release Notes

Version 2.6.0
Platforms: Windows, Linux
Created: November 28, 2011

What’s New
  • Licensing is now enforced on number of concurrent users logged in


Fixed Issues
  • Fixed single server edge case setup (#12414)
  • Fixed issue where polling thread randomly dies (#12334)
  • Updated Apache log level from emergency to error (#12648)


Known Issues
  • Users upgrading from Faspex 2.0.10 may have to regenerate their email templates. For example, additional Comments are not included in Welcome Email after upgrade. Workaround: Customize a template, click "Load Defaults" followed by "Generate E-mail and Save." (#12709)
  • “Configuring package directory” error when upgrading from Faspex 2.0.10 to 2.6.0 after renaming the machine name. (#12714) Workaround:
    • After changing machine name and rebooting machine, open the passwd file located under “C:\Program Files (x86)\Aspera\Enterprise Server\etc” for Windows 64 bit server. On Windows 32 bit server, look under “C:\Program Files\Aspera\Enterprise Server\etc”
    • Remove all entries from the passwd file and save the updated file
    • Run upgrade (asctl faspex:upgrade)

Package Information
sha1sums:
  • 22ab094d96011e0dd88c9e55bef429895ce96315 aspera-faspex-2.6.0.47145-0.i386.rpm
  • 6f44d1cf55c9939c018392b9fac7c3d367841ce2 aspera-faspex-2.6.0.47145-0.x86_64.rpm
  • 797af046dfe77f85011cdefc17ffab73681ee449 AsperaFaspex-2.6.0.47145-windows-32.msi
  • 37d487f42bb9dd2ca96feaea534503bb42118628 aspera-common-1.1.5.47003-0.i386.rpm
  • 55466503cdbe15cc60b4a4ac12aa26199fa8003c aspera-common-1.1.5.47003-0.x86_64.rpm


md5sums:
  • 262eb77ab482c4471bf0e17386f03ef8 aspera-faspex-2.6.0.47145-0.i386.rpm
  • a86abbbdad080de3ce508115fe5ded8e aspera-faspex-2.6.0.47145-0.x86_64.rpm
  • 51b9aa6a1ab12b9fea9e63e3f6265ac8 AsperaFaspex-2.6.0.47145-windows-32.msi
  • 8cd222772550829bd3a3870e57a560b9 aspera-common-1.1.5.47003-0.i386.rpm
  • b9bf8c046897a939ba1267af936a6de3 aspera-common-1.1.5.47003-0.x86_64.rpm
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk