AdminAnywhere Changelog

What's new in AdminAnywhere 1.55

Dec 24, 2014
  • FileMaker Server 13 compatibility

New in AdminAnywhere 1.54 (Dec 24, 2014)

  • Improved date parsing for last schedule

New in AdminAnywhere 1.53 (Dec 24, 2014)

  • Added servlet for triggering server schedules, by ID as well as by name

New in AdminAnywhere 1.52 (Dec 24, 2014)

  • FileMaker Server 12 compatibility update.

New in AdminAnywhere 1.511 (Dec 13, 2011)

  • Fixed issue with AdminAnywhere.war file missing from deployment.

New in AdminAnywhere 1.51 (Dec 13, 2011)

  • Fixed issue with retrieving FileMaker Server installation path from registry on Windows when using FileMaker Server 10.
  • Fixed issue where databases from a custom database folder were not being listed.

New in AdminAnywhere 1.4 (Jan 22, 2011)

  • Issue was resolved that was only allowing one plug-in at a time to load on Windows 7 and Windows Server 2008 R2
  • Logging is now consolidated to a single log file for all 360Works plug-ins. This should make it easier to report issues to 360Works, and will also significantly reduce the amount of disk space used when running multiple 360Works plug-ins on FileMaker Server.

New in AdminAnywhere 1.31 (Oct 30, 2010)

  • Now reads from the Windows registry so that it can work with FileMaker installed on a non-standard volume or location
  • Fixed an error that occurred in Windows 7 when trying to get a list of connected users, if there are none.

New in AdminAnywhere 1.302 (Mar 10, 2010)

  • Fixed intermittent problem where plugins may not load in Windows XP in FileMaker 11

New in AdminAnywhere 1.301 (Feb 9, 2010)

  • Now displays visible error message unless SetErrorCapture is on
  • Fixed situations where modal dialogs could appear behind other windows in MS Windows
  • Fixed plugin not loading in Java 6 update 18

New in AdminAnywhere 1.22 (Jun 13, 2009)

  • Now works with 64 bit systems, where FileMaker is in the 'C:Program Files (x86)FileMakerFileMaker Server' folder.