Archive for February, 2007

Worship Assistant 4.51 Released

Saturday, February 24th, 2007

ChurchAssist Technologies is pleased to announce the release of Worship Assistant 4.51. The purpose of this release is to address several issues that were discovered recently in version 4.50:

  • ‘Save Dataset As’ often aborted with error message concerning files opened by another process.
  • Rebuilding data files sometimes aborted with error message concerning files opened by another process.
  • Printing to PDF did not render with the correct font under certain circumstances.

(For those of you who might have missed the announcement for version 4.50, the list of changes and fixes is included at the bottom of this message.)

Version 4.5 is a free upgrade to anyone who has purchased version 4. To upgrade, simply download and run the installer from the link below. There is no need to uninstall the previous version, but we do strongly recommend you make a backup of your data before installing the new version.

Version 4.51 can be downloaded from the following location:

http://www.churchassist.com/download/wa451.exe

Version 4.50 (January 24, 2006)

Changes:

  • Font and other changes to make the program more compatible with Windows Vista.
  • Minor updates to user interface ‘look and feel’.
  • Eliminated some flashing in the preview window on the Presentation Control Panel.
  • Added item under View menu for showing and hiding the navigator bar (introduced in v4.40).

Fixed:

  • Song Manager - error message when scrolling to the bottom of the ‘All Chords’ list.
  • Browse windows - changes to column ordering or sizes were not persistent.
  • Merge Songs - merging from the bottom list to the top list resulted in an error message.

Last Thursday’s Downtime

Sunday, February 4th, 2007
Here is more information on last Thursday’s downtime:
Beginning at 8:47 PM EST, our network accessibility was impacted by a major fiber cut (near Atlanta), which physically damaged a network line in use by one of our upstream providers. This provider handles what is known as our route advertisement, and because their connectivity was impacted physically, ours was impacted virtually, as traffic was unable to be directed to the datacenter where our server is located.
The provider’s crews worked as quickly as possible to place new fiber and bring things back online, and we’re grateful that they used all their resources to resolve this issue, just as we would utilize all resources available to us to resolve any issue we could control. The network returned to normal at 2:57 AM Eastern US time. During this time, our server was not actually down, and nothing on the servers was affected.
I apologize for the inconvenience! We don’t like downtime any more than you do, but there is nothing we can do to prevent this type of thing from impacting us. Fortunately, it is a rare occurrence!