5.0.x Known Issues and Fixes - viewLinc 5.0

viewLinc 5.0.x Errata

Document code
viewLinc 5.0
Document type
Table 1. Known Issues
Area Description Fix Version
System During an upgrade, if the previously installed viewLinc application data is stored in C:\Program Files (x86)\Veriteq Instruments\viewLinc\db\, Location history data is deleted. SU1
License key number may display in the Events Log. SU1
If upgrading a system that uses single channel private thresholds, upgrade may not complete. SU1
Device discovery does not always work on a fresh system. Services must be restarted. SU1
On upgrade, the UI may freeze while opening a previously configured notification template. SU1
Alarm Messages and Alarm Comments may not be included during upgrade from v4.3.5 SU1
If Location alarming is paused by a threshold alarm schedule, deleting the schedule may interrupt viewLinc restart operation. SU1
Schedule names that use non-ASCII characters may cause intermittent server restarts. Save schedule names with EN (ASCII) characters only. SU2
When a timeout error occurs on a locked Events database, a reboot is required in order to restore Events functionality. SU2
On upgrade, any Location that has been assigned group permissions will not be upgraded correctly. Moving the group permission to the parent zone before upgrade will allow this to upgrade correctly.
Unicode characters in certain user fields may cause viewLinc to not start properly after an upgrade. SU2
viewLinc may not start after upgrade if the system uses measurement units that are not contained in the units table. SU2
Alarms Alarms for "Configuration change failed" and "Configuration changed externally" may be triggered when sending threshold alarm settings to RFL100. SU1
Upgraded systems may not be generating Configuration Database Validation alarms. SU1
Dew point threshold alarms do not trigger if the Location's default units are set as Fahrenheit. SU2
An alarm may remain visible in the active alarm list after it has turned off and been acknowledged. SU2
A user without admin rights may not see any alarm templates if the user goes to the alarm templates tab immediately after login. SU2
Locations linked to HMT140 RTD channels may experience premature Sensor Failure Alarms. SU2

When a threshold alarm is scheduled for the time period 00:00 - 24:00, the alarm incorrectly pauses between 23:00 and 00:00.

Workaround: when the alarm is set for the time period 00:00 - 23:59, the pause affects only the alarms occurring between 23:59 and 24:00.

When a trend is unusually long (for example, it includes multiple locations on one graph and the duration is over a month), the device scan may be delayed. If the delay occurs, a device scanner error alarm is triggered.
Devices A "Description changed externally" event appears when enabling a channel in a DL data logger.
Moving a currently existing network DL data logger to a different Device Host may cause communication problems. SU1
HMT140 devices are not always cleared from the New Devices window after being accepted. SU1
Unlinked channels on HMT140 devices may be deactivated when editing device settings. SU1
Logger scan stoppages trigger additional Host Configuration Alarms. SU1
Disconnecting RFL100 data loggers may not trigger a Communication Alarm. SU2
Communication failure between viewLinc and DL data loggers may result in excessive memory usage. viewLinc Enterprise Server or Device Host may require a restart.
HMT330 devices may not get added using a manual file upload.
When swapping RFL100 loggers, start timestamp information may get overwritten by last swap timestamp.
Probe swapping T+RH probe with T+T probes: Location history displays T on the RH history table. SU2
Duplicate AP10 serial numbers may display in viewLinc. If an AP10 is connected to viewLinc using an IP address, and then deactivated, make sure to activate the device in the AP10 web interface using the viewLinc IP address, not the hostname.
When using a TMP115 dual probe setup with RFL100, the order of the probes displayed in an Edit Device Properties window can be reversed. SU2
Reports Scheduled reports are still generated after the report owner is deactivated.
Device information is not shown correctly in Location History reports after a probe is changed. SU2
After modifying or creating reports, a viewLinc Enterprise Server restart may generate false Database Validation alarms indicating that report records were modified outside of the viewLinc application. SU1
HMT330 probe serial number is not printed in the Location summary table.
In exceptionally busy systems, the report generator may fail without notifying the System Administrator. SU2
Changing RFL100 loggers twice in quick succession results in the timestamp not being reported correctly in a Location's History Report. SU2
Location History Report shows the wrong second probe serial number in the Device History table when a dual probe setup is used. SU2
Very large Event queries may lock the Events database and prevent writes to the Events database. When this happens, viewLinc services require a restart. This failure to write events is not logged and the System Administrator is not notified. SU2
When a Location History Report is generated, the graph presentation in the report may display the threshold lines and threshold line colors incorrectly.
UI Sample counts on a trend graph may display incorrectly. SU1
Find in Tree and Trend menu options appear enabled on an unlinked channel. SU1
In Views Manager, the UI may need to be refreshed if a user tries to create a view on filtered results.
User password displays in the address bar in mobile interface. To fix this issue, please contact technical support. SU2
Trend scale does not accept 0°C as a fixed scale setup for a trend SU2
When using the viewLinc mobile app with the Chrome browser for iOS or Android, the icons for Sites view, Locations view, and Alarms view, on the top right corner of the screen, are not visible. SU2
Removing the Events folder may not generate an Event Validation Alarm. SU2
In viewManager, unlinked Locations will move under the root when a new Location is added to the dashboard and moved to a different folder. SU2
The backund color of a popup window continues to show an alarm condition after the alarm has cleared from the system.

When adding or editing a user in the Users and Groups menu, the Windows authentication method Domain name entry field only accepts alphabetic characters.


Multiple domain names and/or IP addresses cannot be entered for the information used to create the certificate request file. The viewLinc install kit only includes the first name entered in the produced .csr file.

Workaround: This issue has been fixed in the latest version of the CreateCSR.exe file that is available at www.vaisala.com/en/support/viewLinc. Vaisala recommends using one fully qualified domain name.

Other Minor UI display and translation errors. SU1
In viewLinc 5.0 User Guide (M211975) "Installing viewLinc as an Upgrade", step 13, the correct destination directory for backup data is: C:\Users\Public\Documents\Vaisala\Vaisala viewLinc\.
The readme.txt file indicates incorrect system size recommentations. The most current system specifications are available in the Vaisala viewLinc 5.0 Datasheet (B211708).
In viewLinc 5.0 User Guide (M211975), "Installed System Size", a medium system size has been specified as up to 20 devices (400 channels). The correct medium system size is up to 100 devices (400 channels).
E-learning content will be gradually transferred to a new platform (MyLearning, https://mylearning.vaisala.com). The shift to a new platform will make certain training links in the viewLinc Help obsolete. SU2

Support Contacts

Vaisala Helpdesk: helpdesk@vaisala.com

Vaisala Support Portal: www.vaisala.com/support

viewLinc Errata and Service Update Guide: www.vaisala.com/viewlinc-errata