deSide Updater Version 4.0.114 (May 2011)

This is the current production release of the deSide Updater

We have made significant architectural changes that have improved the reliability and responsiveness of both the deSide Updater service, and the deSide Updater application that is used to monitor and control it. These changes have been tested to confirm that they address the specific issues listed below, however we believe that these changes will also address certain other undiagnosed intermittent issues that have arisen on customer sites from time to time.

EZTUA-58: deSide Updater periodically stops updating when running as a service
The reliability of the update service has been significantly improved, and it has undergone continuous hours of operation testing. If the host machine goes into power-saving mode, or hibernates, or is restarted, then the service resumes when the system returns to normal operations, and the updater updates the data to the current period.

EZTUA-61: The Service can get into a state where it is downloading files, but not processing them
There has been a significant architectural revision to the Updater and this error is resolved as a result of these changes.

EZTUA-67: deSide Updater not always responsive to stop command
The service previously waited until all pending processing operations were complete before exiting. This behavior has been modified so that the service will cancel these pending operations and will exit in a timely way in response to a stop command initiated by an end user.

EZTUA-19: Running multiple copies of the deSide Updater GUI at once causes the updater to stop updating.
This scenario has been re-tested and no problems were found when running multiple copies of deSide Updater GUI in the specific case where deSide Updater is running as a service. Global-Roam recommends, however that you do not run more than one instance of the deSide Updater GUI at any one time as this can cause problems when running in Application mode.

UPD-23: The Updater mangles the DateTime values for some database fields when run in a daylight savings timezone.
When running the Updater with the system clock set to a daylight savings timezone, the Updater was changing some of the Date/Time fields in files being processed into the database by an amount equal to the daylight savings offset (i.e. an hour). For some customers who make use of historical data using the deSide Client Analysis feature, this problem may cause historical reports to fail, and repairs to the database may be required. Please contact global-roam technical support if you are experiencing such problems.

DSD-510: deSide data update service fails to start on machine restart
The deSide Updater service would occasionally fail to start when the host machine was restarted on Windows XP. This problem was due to timeout issues when deSide Updater was trying to make use of system resources that were themselves restarting. This problem has been resolved and the deSide Updater service should now restart as expected when the host machine is restarted.

EZTUA-88: If the program cannot contact the global-roam hosted configuration service, and you already have configs, you cannot continue (but you should be able to).
The deSide Updater will now restart normally in circumstances where it cannot contact global-roam servers to refresh its locally cached configuration files.

EZTUA-60: Items logged in the EventLog are always classified as Information, regardless of content.
EZTUA-81: deSide Updater Australia's event log entries are missing event source information
Logging has been revised and log messages now contain correct data when being written to the Windows EventLog.

TOI-77: Upgrade deSide Updater to .NET 4
The application now runs against .NET 4.0.

---

deSide Updater Version 3.1.4 (August 2010)

This release of the deSide Updater is a maintenance release.

DSD-607: When creating connection for database, can't always create new database
The mechanisms for creating a new database on first installation now behave as expected.

DSD-463: Clicking the 'X' on the Data Source Setup when starting deSide will allow you to continue without doing validation
Added a new button to the form that is displayed during startup to setup the DataAccessManager. The new button is titled "Ignore and Continue", and gives the functionality to ignore all data sources in error, and continue into the application.

DSD-462: The deSide Updater will delete database connection strings from its configuration under certain error conditions
The deside Updater would loose its database configuration if it attempted to connect to a database that was unavailable for some reason (e.g local network problems). This is now fixed.