Vaisala Veriteq viewLinc 3.6.1.406 Release Notes - May 16, 2011 What is new in version 3.6.1.406: New features added and feature modifications in 3.6.1.406: - No new features in 3.6.1.406. This is a maintenance release Issues Corrected: - There was an issue where alarm activation delays were ignored on the second and subsequent threshold excursions. - There was an issue where the 'Edit Threshold' popup title displayed 'XEdit Threshold' - There was an issue where an acknowledged alarm would appear as 'Not Acknowledged' in the 'Channel Graph' pop up window. - There was an issue where an alarm restored message was sent when an alarm that had an activation delay cleared before the activation delay expired. Errata Notes General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have their time synchronized with an accurate source at least once a day. Help: - viewLinc Help is not localized in German. - If the locale language is changed in viewlinc.cfg after installation, the browser cache must be cleared to see the correct localized help files. UI: - Clicking repeatedly very fast around the UI tabs may generate a javascript exception. - Channel views on Internet Explorer 9 only work in compatibility mode. - If an exceptionally large value is entered into a threshold (> 1000000000), channel view graphs may not work. Alarms: - No known issues. System: - Ensure that only one viewLinc administrator is activating, deactivating, or swapping loggers at a time. - When editing user contact schedules, if a new schedule is created and named 'Always' or 'Never', viewLinc startup errors may occur. Reporting: - When a manual report is started while scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as “Queued”. The status will remain “Queued” until the queue gets to this report. Depending on the size and quantity of reports already in the queue, this could be a significant period of time. - Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time. - If viewLinc is installed on an English Windows XP/2003 system and run in Chinese or Japanese, the ‘Install files for East Asian languages’ option must be selected in Control Panel\Regional and Language options. Logger Swapping: - When swapping loggers it is important to allow the new logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. - If a logger that is to be swapped in is linked to a vLog Audit Trail, the swap will fail. This is by design. 300 Series Transmitters: - The Firmware version must be 5.04 or later. - It is recommended to upgrade to firmware version 5.10 wherever possible. (Please contact customer support if in doubt.) - 300 Series Transmitters without LOGGER-1 modules do not support historical data backfill. - If 300 Series Transmitters are configured with timeouts greater than the viewLinc scan period brief configuration alarms may occur. POS: -The POS terminals will show alarms when alarms are detected, even if an alarm activation delay is set. For an updated Errata list, please see http://www.veriteq.com/support/viewlinc/errata-viewlinc-3.6.htm *********************************** Vaisala Veriteq viewLinc 3.6.0.398 Release Notes - April 20, 2011 What is new in version 3.6.0.398: New features added and feature modifications in 3.6.0.398: - The color of an individual channel in a channel history report may be manually selected from a default color palette. - Additional language localization for French, Chinese, Japanese has been added. - viewLinc now supports the Vaisala 300 series transmitters as well as the Vaisala Veriteq Loggers. Issues Corrected: - There was an issue where changing the remote host machine name would cause a permanent communications alarm. - There was an issue where reports would hang if the start date was in the previous year. - There was an issue where logger swap would fail when the logger had inactive channels. - There was an issue where an exception could occur when printing the Events. - There was an issue where failed transfers due to folder privileges was not reported correctly. - There was an issue where Temperature units in the Pop-up and Event log did not match. - There was an issue where a failed report did not generate an email. - There was an issue where My channel updates could freeze due to low activity. - There was an issue where communication alarms occurred when a host was added with no installed loggers. - There was an issue where database recover on startup only checked the previous 12 months. This could result in system failure after power outages. - There was an issue where no cause of error was received when an email was generated due to report failure. - There was an issue where disabling a threshold would not terminate an active alarm. - There was an issue where a failed logger swap would generate a configuration alarm. - There was an issue where viewLinc would fail if the database files were located on a network drive. - There was an issue where the POS service would hang to all POS terminals if one connecting Digi lost power. - There was an issue where viewLinc starting up would set the Archive bit on all the db files even if they were not written to. - There was an issue where a large report could result in memory exhaustion and viewLinc failure. - There was an issue where installation upgrades would fail to stop the running viewLinc service. - There was an issue where resuming a paused channel would not generate an event log. - There was an issue where scheduling reports monthly would be 31 days. - There was an issue where deactivating a block of thresholds would fail if any were already deactivated. - There was an issue where POS terminals would not display all channels if there were more than 5 terminals. - There was an issue where unnecessary UI disconnects could occur on poor network connections. - There was an issue where viewLinc would sometimes take > 2 minutes to shutdown. - There was an issue where Alarm History Report details would show incorrect email information. - Many small issues with the user interface have been corrected. Errata Notes General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have their time synchronized with an accurate source at least once a day. Help: - viewLinc Help is not localized in German. - If the locale language is changed in viewlinc.cfg after installation, the browser cache must be cleared to see the correct localized help files. UI: - Clicking repeatedly very fast around the UI tabs may generate a javascript exception. - Channel views on Internet Explorer 9 only work in compatibility mode. - While editing thresholds, the title bar appears as ‘XEdit Threshold’ in all languages instead of ‘Edit thresholds’ in the appropriate language. - If an exceptionally large value is entered into a threshold (> 1000000000), channel view graphs may not work. Alarms: - Alarm activation delays are ignored applied on the second and subsequent threshold excursions. System: - Ensure that only one viewLinc administrator is activating, deactivating, or swapping loggers at a time. - When editing user contact schedules, if a new schedule is created and named 'Always' or 'Never', viewLinc startup errors may occur. Reporting: - When a manual report is started while scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as “Queued”. The status will remain “Queued” until the queue gets to this report. Depending on the size and quantity of reports already in the queue, this could be a significant period of time. - Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time. - If viewLinc is installed on an English Windows XP/2003 system and run in Chinese or Japanese, the ‘Install files for East Asian languages’ option must be selected in Control Panel\Regional and Language options. Logger Swapping: - When swapping loggers it is important to allow the new logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. - If a logger that is to be swapped in is linked to a vLog Audit Trail, the swap will fail. This is by design. 300 Series Transmitters: - The Firmware version must be 5.04 or later. - It is recommended to upgrade to firmware version 5.10 wherever possible. (Please contact customer support if in doubt.) - 300 Series Transmitters without LOGGER-1 modules do not support historical data backfill. - If 300 Series Transmitters are configured with timeouts greater than the viewLinc scan period brief configuration alarms may occur. POS: -The POS terminals will show alarms when alarms are detected, even if an alarm activation delay is set. For an updated Errata list, please see http://www.veriteq.com/support/viewlinc/errata-viewlinc-3.6.htm *********************************** What is new in version 3.5.2.277: New features added and feature modifications in 3.5.2.277: - No new features, this is a maintenance release. Issues Corrected: - There was an issue where viewLinc did not restart if unexpected system errors caused the DB access to fail. - There was an issue where the worker would quit unexpectedly with Loggers that are linked to a vLog Audit Trail. - There was an issue with Alarms not always sending notifications if there were multiple notifications assigned. - There was an issue with resource leaks under certain conditions. - There was an issue where Modifications to Alarm Templates were not always logged if they had no notifications assigned. - There was an issue where Creating batch thresholds was limited to a maximum of 10 at a time. - There was an issue where Reports used excessive memory and high CPU when there with a high alarm count. - There was an issue where My Channels updates could be excessively slow when high Logger counts selected. - There was an issue where Detailed Alarm reports could show the wrong Alarm creation time. - There was an issue where the Alarm Report summary was incorrect when Loggers,Channels, or Thresholds were deactivated while there was an active alarm. - There was an issue where Logger timestamps were incorrect if a Logger was cleared twice within a scan interval. - There was an issue where a Logger swap would find a Logger on a different remote host if the COM ports were the same. - There was an issue where the Logger status would incorrectly show 'OK' if it was disconnected while paused. - There was an issue where the watchdog would not connect if there was a Web proxy configured on the system. - There was an issue where communications would fail on Windows 7. - There was an issue where the server hostname would not update if it was changed. - There was an issue where Alarms that were not acknowledged promptly would cause excessive data base sizes. - There was an issue where upgrading from older versions caused system preferences to be incorrectly merged. - Alarm email notifications have been modified to include the value at the time of the alarm, and the current value + timestamp. - Improvements have been made to the UI performance. - Many small issues with the user interface have been updated. Errata Notes: General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have their time synchronized with an accurate source at least once a day. - When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved. UI: - Channel updates in the browser may stop refreshing on low-activity systems and the server has disconnected message may appear. The workaround is to refresh the browser. Alarms: - Threshold Alarms generated during a backfill, and deactivated during the backfill, will not send activation notifications. The deactivation notification will be sent. The workaround is to add the template macros [AlarmTimestamp] and [AlarmValue] in the 'Threshold Restored' email template. System: - Ensure that only one viewLinc administrator is activating, deactivating, or swapping loggers at a time. Reporting: - When a manual report is started during a time when scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as "Queued". The status will remain "Queued" until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already in the queue. - Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time. - 'Monthly' reports are actually 31 days, not calendar months. Logger Swapping: - If a Logger that is to be swapped in is linked to a vLog Audit Trail then the swap will succeed, however, the descriptions will revert to what they were before swap on the next update. The workaround is to ensure that loggers are not linked to a vLog audit trail before attempting to swap. - When swapping loggers it is important to allow the new Logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. For an updated Errata list, please see http://www.veriteq.com/support/viewlinc/errata-viewlinc-3.5.htm *********************************** viewLinc 3.5.1.266 Release Notes - July 14, 2010 What is new in version 3.5.1.266: New features added and feature modifications in 3.5.1.266: - Zone and Channel Permissions: Users can now be assigned a set of channels or zones that they will have permissions view. - New user permission level: The Configure Custom Thresholds permission level has been added so that users with limited access to the system (assigned channels and zones) can still manage thresholds for the channels that they are assigned. - User Schedules: Schedules that define a user’s hours of availability or responsibility can be created and assigned to users. These schedules are used with alarm notification options to determine if and when the notifications should be sent to a user. - Email Notification User List: A new field has been added to the alarm email notifications to specify a user or list of users as alarm notification recipients. These notification emails will be sent according to each user’s schedule. - Logger and Channel Aliases: A new field for Loggers and Channels has been added so that more than 16 and 12 characters, respectively, can be used to describe the logger or channel. These are system names and do not get stored in the logger. - SP Logger Calibration Info: The system has been modified to not display "NA" for calibration information for SP loggers. It will now display "See Calibration Record". - Improved Performance: Performance improvements have been made to the data gathering and processing to reduce the amount of network traffic and to increase throughput for large systems. - Active Sessions: A line has been added to the status bar to indicate the number of currently active client sessions. - Report Graphs Resolution: The resolution of the data that can be graphed in the channel history report has been increased from 2000 points to 10000 points per channel. This reduces the amount of averaging that will occur when the graph is displayed. - Large Channel Resizing: The large channel real-time view has been updated to handle resizing operations. This is useful for smaller displays or when multiple views are open on the same display. Issues Corrected: - There was a possibility that a data timestamp drift may be introduced if communication delays occur. These drifts would trigger configuration errors. - There was an issue when, swapping a logger into the system that had been swapped out, that required logger deactivation and reactivation. - There was an issue with POS displays when a channel assigned to the display was deactivated. - There was an issue when a single remote Host lost connectivity. This would result in all Host being displayed as unreachable. - There was an issue in which saving a report twice without making a change would cause the browser to hang. - There was an issue in which repeat email notifications where not translated to German. - There was an issue where transfers would fail due to transfer file names when running in German. - There was an issue with the status column when exporting the Events tab to Excel when running in German. - There was an issue where there could be a memory leak when generating reports. - There was an issue where a failed attempt to connect to an SMTP server would block the UI. - There was an issue where upgrading a system that had deactivated users would cause the Watchdog to continuously restart the viewLinc Service. - There was an issue where logger backfill data that was not in the current month could be stored in the current month's database. - There was an issue where the threshold lines on a channel history report would force the graph to be drawn to include the last date and time when the threshold limit was modified. - Improvements have been made to the Alarm Template Macro handling. - Many small issues with the user interface have been updated. Errata Notes: General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have its time synchronized with an accurate source once a day at a minimum. - When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved. - If viewLinc was upgraded from version 3.4.5 or earlier to version 3.4.6 and is now being upgraded again to viewLinc 3.5.1, then ensure that the System Preferences and Email Settings have been imported correctly after the upgrade process. Alarms: - User with security levels of "Configure Alarms" OR "Configure Custom Thresholds" can deactivate thresholds. However, the "Show Deactivated Items" button is not available to these security levels. Therefore these user levels are unable to view deactivated items and are also unable to reactivate thresholds that have been deactivated. - The alarm restored notification may not get triggered if there are multiple actions associated with an alarm. For example; a pop-up, command line and email notification. The work around here is to not have the delays for each notification the same. Offset each notification by one minute. - If an alarm template is created without notification actions the event will not get logged. The template will still function as required. The work around is to always include a notification action when creating alarm templates. - The Current Value that is sent in the threshold alarm email notifications is the value that was recorded when the alarm was triggered, not the current value. The workaround for this is to edit the Threshold Repeat and Restored template and remove the line with “Current Value: [ChannelValue]”. This will removed the incorrectly labeled text from the templates. - When creating batch threshold alarm settings in the System tab only 10 channels should be done at a time. If more than 10 channels are tried, then some settings will not get assigned to the channels. - Alarms that require acknowledgement should be handled promptly. The system database can grow substantially if a large volume of alarms are left in the Active Alarms Tab. Reports can fail to generate if the databases get unusually large. System: - Ensure that only one viewLinc administrator is activating, deactivating or swapping loggers at a time. - The viewLinc resolved Host name only happens at first time run. If the server name changes after that it will not be reflected in viewLinc. Reporting: - When a manual report is started during a time when scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as "Queued". The status will remain "Queued" until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already in the queue. - Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time. Logger Swapping: - When swapping loggers it is important to allow the new Logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. For an updated Errata list, please see http://www.veriteq.com/support/viewlinc/errata-viewlinc-3.5.htm *********************************** viewLinc 3.4.100.533 Release Notes - April 20, 2010 What is new in version 3.4.100.533: New features added and feature modifications in 3.4.100.533: - Tab separated historical reports for import to Excel can now be generated as well as pdf reports. - Internationalization for German has been added. - The ability to deactivate thresholds has been added. - Support for TdC (Dew point) as a temperature unit has been added. - Time zone information in reports and exported files has been added. - A Zone column has been added to the My Channels table so that the channels can be sorted by zone. - The IP addresses for vNet and Digi devices have been added to the System|Loggers loggers table. - An icon to indicate that a threshold is enabled or disabled has been added to the System|Loggers thresholds table. - Repeat notifications will now continue to be sent after server/service restart. - Notification of alarm deactivation will now honor the alarm notification delay. A deactivation notification will not be sent unless an activation notification has been sent. - New timeout parameters, such as worker timeout and Watchdog timeouts, were made configurable to help administer large systems. - Watchdog messaging has been improved. All watchdog restart events messages are now sent to the viewLinc admin. Previously only failed attempts were sent. - Watchdog and POS agents now log in without using a database account. The viewer account is no longer used so the event log will not show viewer user logins by the system. Issues corrected in 3.4.100.533: - Localized timestamps in printable pages for the Event and Alarm tabs now show the correct localized time. The timestamp in previous version were displaying the viewLinc server time. - Added database access synchronization: records are now locked for modification, so that multiple threads cannot modify the same record at once. This is an enhancement to the thread locking that was done in 3.4.6. Under extreme load testing it was still possible to occasionally get broken links in the sqlite db. This was under conditions that would require several hundred users making changes to thresholds or templates at the same time. This is not a likely user situation but this change ensures configuration integrating. - Fixed threshold line display issues on Channel realtime graphs and reports that involve disabling/re-enabling or deactivating/reactivating thresholds. This corrects the display of threshold lines and removes the requirement to resave thresholds at the beginning of each month. - Fixed duplicate/multiple transfers and report generation and their associated emails. - The database recovery process on viewLinc start has been improved. We have improved the sqlite integrity checking at to account for other possible linking issues that may have been created by earlier versions. - The application configuration files are automatically updated for newly added items. Previous version required the new items to be manually added when upgrading. - Host communication error handling has been improved, as well as issues with multiple entries for the same host. - An issue with displaying multiple swapped logger serial numbers in reports has been corrected. - An issue where the viewLinc admin could save blank passwords for users has been corrected. viewLinc authentication now requires a minimum of four characters. - Some event type classifications have been changed to the appropriate type (e.g. transfer events are now transfer events instead of admin events). - The Logger Configuration Alarms now honor the alarm delay and will only trigger after the delay has expired. - The threshold edit form in the System tab does not have items enabled for edit when templates are specified. - Sorting by host name in loggers or channels tables (both in Zones/My Channels and Reports) does not cause the table to fail to render. - When the system or a logger has been offline for a period time and then comes back online, any thresholds alarms that happened during the offline time will now issue a Threshold Alarm message and a Threshold Restored Message if applicable. - Loggers/Channels can now be left in the "Unassigned Zone" without causing problems with reports. However, we recommend that the channels be moved to zones for ease of use. - Text fields can now accept more than 256 characters where applicable. - Short intermittent communications alarms should now not be seen when using viewLinc Logger Hosts. - When adding predefined comments to Alarm Templates and Threshold Templates, additional text does not need to be added to the comment to ensure that it will be stored in the template. - In the case of a Logger Alarm (Calibration, Configuration, Validation) being triggered, the status of a channel as reported in the real time trending window will display correctly. - When using the “Add Logger” function to add a new data logger to the system, any existing data in the logger is now copied into the database. - Blank passwords now cannot be used or entered when viewLinc authentication is being used. - Loggers can now be freely moved from Hosts to the Enterprise Server. - It is no longer required for a logger to be cleared before being swapped in as a replacement logger. However, we recommend that the logger be allowed to come to equilibrium before being swapped in. Errata Notes: General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have its time synchronized with an accurate source once a day at a minimum. - When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved. System: Large systems (1000 or more channels): - If viewLinc takes a long time to process logger updates (longer than 30 minutes), The Watchdog may restart viewLinc Enterprise service. Workaround: To prevent the Watchdog from restarting viewLinc prematurely, increase the following parameters in viweLinc.cfg file: in "watchdog" section, set minumum_timeout_min to be about 1.5 times longer than a typical update cycle and maximum_timeout_min twice that value. Then restart the viewLinc Watchdog and Enterprise Server services. - Processing updates from a large number of loggers may cause high CPU usage and make the viewLinc UI slow to respond. Workaround: viewLinc can process updates at a slower rate, which will decrease CPU use and allow it to respond to UI requests. To control the speed of update processing, we can change the following two parameters in viewLinc.cfg file: in "performance" section, the processing_gap_sec and logger_batch_size. Please contact Veriteq Technical Support before modifying these parameters. - Turning viewLinc Server off or disconnecting its loggers for a prolonged time will cause slower update cycles when data updates resume. This happens because viewLinc has to catch up with the data samples that were taken while offline, and may have a noticeable effect on a large system. Workaround: For the time while viewLinc is catching up with the "offline" logger samples, it may help to shut down Watchdog service, so that it does not restart viewLinc during the slow initial update cycle. Be sure to restart the Watchdog service after the updates resume with normal update intervals. - The UI may miss the status update. This will cause the UI to display an incorrect number of hosts, loggers, channels, or thresholds in the status line, or show an incorrect update interval. Workaround: Refresh browser window. - Using a large number of channels in My Channels screen may cause the table to fail to refresh because of timeout. Workaround: Use a limited number of channels in My Channels view (50 or less will always work, 100 will work in most cases). Normal Systems (less than 1000 channels): - When deactivating or reactivating a large number of loggers (50 or more) in one operation, the UI may timeout and report that the operation failed, even though it succeed. Workaround: Reload Hosts table or refresh browser window after receiving the error message. - Deactivating, reactivating, or swapping loggers from multiple client sessions simultaneously is not supported and can lead to errors. Please make sure that when you are deactivating, reactivating, or swapping loggers, other users are not performing one of these operations at the same time. Workaround: In case of abnormal system behavior caused by concurrent logger deactivations/reactivations/swaps (for example, logger updates are not happening, portions of UI fail to load, unexpected errors in the log, etc), restart viewLinc Service. Alarms: - Ensure that the delay for Calibration Alarms is set to 0. This is to prevent artificial ballooning of the historical database. - When a logger has been set to start in the future a communication alarm is generated instead of a configuration alarm. Reports: - When a manual report is started during a time when scheduled reports are running or other users are generating reports, the status of the manually generated report is listed as “Queued”. The status will remain “Queued” until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already in the queue. - Due to the time required to generate reports, it is recommended that scheduled reports be set up to start during non-peak times and have at least 15 minutes between each report. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best not to schedule reports with large data sets to start at the same time. - For reports based on a fixed period in the past, alarm duration may be calculated incorrectly, if alarm deactivation was not covered by the report time range. Workaround: Extend report time range to try to include the entire lifespan of the alarm. Logger Swapping: - When swapping loggers it is important to allow the new Logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. Real-Time Display: - In Channel View, vertical axis sometimes shows values formatted incorrectly (e.g. 10.10 instead of 11.0). There is currently no workaround for this. POS Display: - If a channel that used on a POS display and it is deactivated, the POS display will show "Host error", even though the rest of its channels are available. Workaround: After deactivating a channel that is displayed on a POS display, remove the channel ID from line for that POS display in the config file and then restart POS service. *********************************** viewLinc 3.4.6.2968 Release Notes - Jan 27, 2010 What is new in version 3.4.6.2968: - The requirement to clear the browser cache on client PC's has been removed. This will help administer upgrades. - The install now adds the viewLinc Logger Host service to the Windows firewall exception list. - The install now makes a backup copy sqlite config database when upgrading. Installation Note: Following the post-installation reboot, please restart the viewLinc Enterprise Server 3.4 service once in order to enable the auto-correction features. To restart the service go to Start>Run, type services.msc and click OK, then find viewLinc Enterprise Server 3.4 in the list, right-click it and select Restart. Errata Notes: - All errata items remain the same as 3.4.6.2963 except for the need to clear browse cache. *********************************** viewLinc 3.4.6.2963 Release Notes - Jan 20, 2010 What is new in version 3.4.6.2963: - Threshold template modifications were not propagating to the channel thresholds when changing a threshold template to use a different alarm template. This issue only occurred if the threshold template was set to use a different alarm template than the original one selected. This issue has been corrected. - The internal database access has been updated to use thread locks for current transactions. This reduces the possibility of partial writes from happening. - The application shutdown process has been updated to ensure proper database closure on system and service stops. - The application startup process has been updated to recover (if possible) or discard any unprocessed transactions that may be pending from an unclean shutdown and to clean large database environment files. - The Host update process has been updated to avoid premature completion. The side effect of this was intermittent communications alarms. - UI issue when preconfigured comments are deleted has been corrected. - The ability to stop the automatic refreshing of the Active Alarms tab has been added to allow for better viewing and acknowledging on large systems. - The Watchdog service will now send an email to the viewLinc admin when it restarts the viewLinc service. Errata Notes: - Ensure that all users of the viewLinc system clear their browser cache and cookies after installing any viewLinc service releases. - The logger Configuration Alarm does not honor the alarm delay and will trigger if the condition is found. - The threshold edit form in the System tab has items enabled for edit when templates are specified. When a template is specified, any changes made on this form will not be saved. If you need to make changes to template settings you must do this in one of the Alarms Template tabs. - Sorting by host name in loggers or channels tables (both in Zones/My Channels and Reports) causes the table to fail to render. Workaround: delete viewLinc cookies and refresh the browser. - Double report generation may still happen. There's no workaround, other than deleting the extra report when it is created. - When the system or a logger has been offline for a period time and then comes back online, any thresholds alarms that happened during the offline time may only issue a Threshold Restored Message and not a Threshold Alarm message. Please see notes for version 3.4.2.1791 for more errata information. *********************************** viewLinc 3.4.5.2911 Release Notes - Nov 27, 2009 What is new in version 3.4.5.2911: - When upgrading from earlier versions of viewLinc 3.4 an uninstall is no longer required. All configuration settings are maintained and the new version will be installed. All Data is also maintained. - Under some circumstances the TCP port that viewLinc was configured to use could become unavailable after a viewLinc service restart. This was due to internal locking mechanisms and has now been corrected. However, it is still possible for the port to be unavailable if another application uses it. - 3.4.4 introduced erroneous event log messages indicating that there was missing data on loggers that had sample intervals greater than 10 minutes. This has been corrected. - The initial status for report generation was "Started", this has been changed to "Queued" and will remain that way until processing of that report is started. - Email alarm templates now default to use the date/time the alarm occurred instead of the date/time when the email was sent. This change will effect fresh installs only and not upgrade installs. - The Repeat Threshold Email Template is now being used for repeat threshold alarm emails instead of the Threshold Email Template. - The database temporary cache files are now being cleaned up at service startup. Errata Notes: - The logger Configuration Alarm does not honor the alarm delay and will trigger if the condition is found. - Short intermittent communications alarms may be seen when using viewLinc Logger Hosts. Please see notes for version 3.4.2.1791 for more errata information. *********************************** viewLinc 3.4.4.2869 Release Notes - Oct 1, 2009 What is new in version 3.4.4.2869: - Email addresses that have dashes[-], underscores[_] and dots[.] in the first part of the address are now supported. All RFC-compliant address are now accepted. - Emailed .PDF report attachments will no longer get converted to .DAT file extensions. - Previous versions were adding an extra dot[.] to the end of the report file names. This has been corrected. - Emailed report attachments now have meaningful names. - The vLog API that is used for logger communications has been updated to ensure calls are done in a thread safe manner. - Updates have been made to the logger configuration alarm detections. Previous versions only detected channels being disabled. Loggers that have stopped sampling are now detected. - Both viewLinc and the vLog API have had some updates to debug logging utilities. - When discovering new loggers it was possible to have 3 data points in the historical database duplicated with a 10 second offset for existing loggers/channel. This has been corrected. Errata Notes: - The logger Configuration Alarm does not honor the alarm delay and will trigger if the condition is found. Please see note for version 3.4.2.1791 for more errata information. *********************************** viewLinc 3.4.3.1823 Release Notes - Aug 20, 2009 What is new in version 3.4.3.1823: - There have been some internal performance changes to better support extremely large installations (400+ loggers). - Passing large amounts of data for reports has been enhanced so the UI does not appear to be non-responsive. -Logger calibration alarms have been updated so the 3 month and 1 month before due notifications are removed from the alarm list after being acknowledged. - Only enabled thresholds for a channel will be displayed in the My Channel table Threshold summary column. - Some additional error control and recovery enhancements have been added and improved on. Errata Notes: Please see note for version 3.4.2.1791 *********************************** viewLinc 3.4.2.1804 Release Notes - July 14, 2009 What is new in version 3.4.2.1804: - updated the upgrade scripts to better handle upgrades from viewLinc versions 3.0, 3.2 and 3.3 to version 3.4 Errata Notes: Please see note for version 3.4.2.1791 *********************************** viewLinc 3.4.2.1791 Release Notes - July 10, 2009 What is new in version 3.4.2.1791: - greatly improved error recovery and added a new viewLinc watcher process to ensure that the service is running - added new critical event notification that will let the viewLinc administrator know of fault conditions by email - added support for non English characters - modified the channel history report table data format to continue the table to the pages to the right Errata Notes: General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have its time synchronized with an accurate source once a day at a minimum. - When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved. - Do not keep loggers in the “Unassigned Zone”. For correct reporting results, channels must be in a user created zone. - Do not enter more than 256 characters in text fields Alarms: - When adding predefined comments to Alarm Templates and Threshold Templates, additional text must be added to the comment otherwise it will not be stored in the template. - In the case of a Logger Alarm (Calibration, Configuration, Validation) being triggered, the status of a channel as reported in the real time trending window will display as “Communication Alarm”. System: - When using the “Add Logger” function to add a new data logger to the system, any existing data in the logger is not copied into the database. To insert a new logger into viewLinc with backfilled data, use the “Discover Logger” function. - If changes are made to permissions while editing a user, the user’s password must be re-entered before saving otherwise the password will be blank. This is only the case when viewLinc security is being used. - Once a logger has been discovered on a specific host machine (either the main server or a remote host) it cannot be rediscovered on a different host. Reporting: - When a manual report is started during a time when scheduled reports are running, the status of the manually generated report is listed as “Started”. The status of the report will remain “Started” until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already scheduled in the queue. - Due to the time required to generate reports it is recommended that scheduled reports be setup to start during non-peak times. This will reduce the chance of a scheduled report delaying a manually requested report. It is also best to not schedule reports with large data sets to start at the same time. - To reduce load on the server schedule reports with at least 15 minutes between them Logger Swapping: - The new Logger needs to be left on the COM port for 3 logger sample intervals or have its internal memory cleared before swapping the logger. Otherwise there will be up to 3 data points overlapped in channels historical data. - When swapping Loggers it is important to allow the new Logger to come to equilibrium before placing it on the COM port. This will ensure that data recorded from outside of the environment is not included on reports. Real Time Display: - Real-time data points are sometimes posted to the real time graph twice for the same data point. This causes a vertical line to appear at the data point. The timestamp and the value for the two points are identical. The readings in the database are correctly stored as just a single measurement at these points. - Threshold lines will not show activated/deactivated events. If the threshold was deactivated and then activated the line will start at the new activation time. This also occurs when the threshold is enabled and disabled. For an updated Errata list, please see www.veriteq.com. *********************************** viewLinc 3.4.1.1703 Release Notes - June 8, 2009 What is new in version 3.4.1.1703: - fix for an issue where spikes could be introduced in the historical data - fix for an issue where the historical data timestamps could start to jitter which would result in data overlap - fix for an issue where the user could delete threshold templates and cause the alarm history for that threshold not be reported - fix for an issue where deactivated channels were not showing up in the Report Source Data selection form - fix for an issue where report queues could not be longer than one hour - alarm and threshold templates cannot be deleted - threshold alarms that have been added to channels cannot be deactivated (they can be enabled or disabled) Errata Notes: General: - To ensure data timestamp accuracy, verify that the viewLinc server time is set accurately before installing the viewLinc software. The viewLinc server and logger host should also be set to have its time synchronized with an accurate source once a day at a minimum. - When entering text in various fields of the forms, it is necessary to tab out of the field or select another field for the new values to be saved. - Do not keep loggers in the “Unassigned Zone”. For correct reporting results, channels must be in a user created zone. - When non-English versions of Windows are used, viewLinc “Zone” names should only include ASCII characters. Alarms: - When adding predefined comments to Alarm Templates and Threshold Templates, additional text must be added to the comment otherwise it will not be stored in the template. - In the case of a Calibration Alarm being triggered, the status of a channel as reported in the real time trending window will display as “Communication Alarm”. System: - When using the “Add Logger” function to add a new data logger to the system, any existing data in the logger is not copied into the database. To insert a new logger into viewLinc with backfilled data, use the “Discover Logger” function. - If changes are made to permissions while editing a user, the user’s password must be re-entered before saving otherwise the password will be blank. This is only the case when viewLinc security is being used. - Once a logger has been discovered on a specific host machine (either the main server or a remote host) it cannot be rediscovered on a different host. - When non-English versions of Windows are used, viewLinc authenticated user passwords should only include ASCII characters. Reporting: - When a manual report is started during a time when scheduled reports are running, the status of the manually generated report is listed as “Started”. The status of the report will remain “Started” until the queue gets to this report. This could be a significant period of time depending on the size and quantity of reports already scheduled in the queue. - Due to the time required to generate reports it is recommended that scheduled reports be setup to start during non-peak times. This will reduce the chance of a scheduled report delaying a manually requested report. Logger Swapping: - The new Logger needs to be left on the COM port for 3 logger sample intervals or have its internal memory cleared before swapping the logger. Otherwise there will be up to 3 data points overlapped in channels historical data. Real Time Display: - Real-time data points are sometimes posted to the real time graph twice for the same data point. This causes a vertical line to appear at the data point. The timestamp and the value for the two points are identical. The readings in the database are correctly stored as just a single measurement at these points. *********************************** viewLinc 3.4.0 build 1660 Release Notes - May 22, 2009 What is new in version 3.4.0 build 1660: - Historical Alarm Reports - Historical Channel Reports - Alarm Templates - Threshold Templates - Logger Swapping - Recalibration Alarms - Logger Validation Alarms - Log File Validation - Remote Logger Host - Live Channel Graph - Ability to restore previously deactivated logger hosts, loggers, thresholds, transfers, and user accounts - Numerous bug fixes *********************************** What is new in version 3.3.1 build 4004 VL: - Snooze alarms (alarming can be paused/resumed as user needs it) - Alarms, threshold, acknowledgement free-form comments can be selected from a predefined list - fix for a known problem when logger could not be configured - fix for known logging problem - fix for 'port got stuck' problem *********************************** What is new in version 3.3.0 build 768 VL: - support for Unicode; it works with international versions of Windows OS - improved security; session expired feature is implemented - free-form comments can be added to alarms, transfers, log records - pop-up notification for threshold and communication alarms - active alarms list can be exported in to an Excel format and printed as a report - Remote Host is not supported - Remote Display is not supported - Password policies for viewLinc authentication are not supported *********************************** Upgrade from version 3.x. - During the installation of v3.4.0 build 1660 VL, if you have an existing installation of v3.x, you will be presented with the option to convert v3.x data into v3.4 format. If you select this option, setup imports the data automatically and disables the old v3.x installation. If you decide to skip this step then an empty DB will be installed. *********************************** For questions or help, please contact us at 1-866-861-3388 (8am-4pm PST). Outside of North America, call +1-604-273-6850.