5.1.x Known Issues and Fixes - viewLinc 5.1

viewLinc 5.1.x May 2025 Errata
Product status
Document code
DOC253281EN
Revision
C
ft:locale
en-US
Product
viewLinc 5.1
Document type
Errata
Known Issues
Area Description Fix Version
Alarms After upgrade to version 5.x, alarm reports could fail to generate on information collected using viewLinc 4.0 or earlier. SU2

If a logger channel is configured with lower case units, threshold alarms generated by the Location that the channel is linked to will not appear in alarm reports.

Workaround: use the viewLinc Events page to filter the events for the time period of interest and the Locations that were impacted. Then export the listing to produce the desired output.

SU3
The alarm report always shows 0 alarms for the dew point channel of the VL2000 logger even when there are active or acknowledged alarms for that channel. SU3
The Threshold Summary column of an alarm template always shows the temperature in the summary in degrees Celsius even when the temperature unit is set as Fahrenheit in the preferences. SU3
If a device with a missing probe is connected to viewLinc and the channels of the device are linked to Locations, viewLinc incorrectly produces a Database Validation alarm at each restart. SU9
When using a customized Calibration Alarm Template with delays, calibration alarms are not raised as intended. SU3

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.

 SU4

When a Location uses Fahrenheit units with 0 decimal places as its alarm threshold, rounding issues may prevent the threshold alarm from being generated.

Workaround: Set Locations that use Fahrenheit units to use 1 decimal place more than the required accuracy. This is can be by editing the System Preferences or the Location properties.
Certain device configuration alarms display an empty string in the "Error" column in the alarms grid and email/SMS notifications. The following configuration alarms are affected by this issue:
  • Probe changed, Battery is low, Device clock drift, Product recall - see Events for more details, Device scanner is slow or stopped

The missing error text can be viewed from Events.

 SU4
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. The scanner recovers gracefully once the requested data has been processed. SU4
When DL loggers are used in applications involving high increases or decreases in measurement values, the Data sample inconsistency configuration alarm may be triggered incorrectly. The issue is limited to DL loggers. SU5
When HMT140 loggers are used with viewLinc, the External configuration changed alarm may incorrectly be raised. The false alarm may be sent multiple times.
The original host's Host Configuration Alarm and Host Communication Alarm will be missing from the Alarm report if the logger moves to a different host (DL logger with physical Host PC, and RFL logger with AP10 host).
When using Windows 365 for email authentication, the "send from" report always shows the verification was done via SMTP method and not Windows 365. Version 5.2
If a viewLinc Location is configured with multiple threshold alarms, with each using the same alarm template, it is possible that some of the alarm-on events will not be captured in the Event log. If you want to have multiple thresholds for a single location, it’s recommended that you use a different threshold alarm template for each threshold. Version 5.2

Unlinking or linking a probe will clear any active device alarms for other probes/channels on the same device. For example, if there is a device with two probes, one of which has an active calibration alarm, unlinking the other probe from its Location automatically clears that alarm. Similarly, if a probe is newly linked to a Location, other linked probes on the same device will have their calibration alarms cleared.

 Version 5.2 SU1
System If you have a slow network, it's possible that premature connection failures can occur.
Workaround: Update the following settings in the [web] section of the viewLinc.cfg file (in the C:\Users\Public\Documents\Vaisala\Vaisala viewLinc\config folder) as follows:
  • retired_token_timeout_secs = 120 (the default is 60)
  • request_token_timeout_secs = 1200 (the default is 600)
On large systems, data retrieval may cause processing errors. SU1
It is possible that viewLinc will display a 1-day discrepancy for device calibration dates; that is the calibration date may be displayed as 1 day earlier than expected. This can occur in areas where the local time zone is behind UTC, for example North America. Version 5.2 SU1
Reboot after a timeout error on a locked Events database may cause loss of Events data. SU1
If a user belongs to a group with a view permission for a Location or Zone (for example, the "Everyone" group), the user can still view those Locations or Zones even if a different group the user also belongs to is blocked from viewing them (set to "hide"). SU3
Performing a Windows Update before shutting down viewLinc services may cause database issues in viewLinc. SU3
There is an issue affecting viewLinc between versions 5.0 and 5.1.2, when device hosts are used. (Versions 5.1.3 and newer are unaffected. The CA certificate for these versions expire in 2029.) The issue is due to the Host and CA certificates having expired on 2022-10-08. It affects connectivity between the Enterprise server and any Device Hosts running on these versions and will interrupt data collection and alarming. SU3
When using the REST API interface, setting a date duration (for example, 6 days or 7 hours 15 minutes) for the/rest/v1/locations_history date_from parameter causes an exception. Only an epoch value (seconds) can be used with the parameter. Version 5.2
When there is a disruption in the display client's network, the display client may fail to reconnect to viewLinc after the network is restored. SU5
When a user unsuccessfully attempts to login to a deactivated user account, the event log incorrectly indicates that the login was successful.
When a REST API query is made, each query is incorrectly logged as an event. This can cause performance issues in larger systems with a high number of REST API queries. SU7
Configuration change records may be incorrectly written multiple times to the database file, causing excessive growth of the configuration file in the historical database. SU7
Devices

After calibration, RFL100s are not updated in the viewLinc UI to show the correct calibration date. In addition, viewLinc reports might not show the correct calibration date.

Workaround: To have the correct calibration date displayed on RFLs, reboot the server that viewLinc is running on.

Data logger backfill and real-time data discrepancy in new installation. SU1
The default template for adding a HMT330 Modbus connected device contains some errors that may provide erroneous readings. Contact Customer Support for help with correcting this issue. SU3
Setting a calibration due date for an RFL device in viewLinc prevents setting the due date back to system default. SU3
When Comments on Changes are set to Required in the System Preferences, attempting to link a Patlite tower to a new Location results in an error and the linking fails, if the tower is already linked to a Location. SU3
Attempting to deactivate or save a change to a Location or Zone property for Locations or Zones that are nested 5 levels or more may fail. This happens if a new line character (carriage return) is used in the description of a Location or Zone, or in any of the parent or child nodes of those Locations or Zones. SU4
If there are multiple instances of a Modbus device being used with the same IP address and port number, it is possible that the device cannot manage multiple concurrent accesses for readings. This can result in missing data. SU4
UI The RH grouped average is displayed as N/A in Pop-up and Views Trends. This behavior doesn’t occur in reports.
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. SU9
Customizations to the columns in Locations (for example, reorganized column order or added columns) are discarded at log out. At next login, the view resets back to default. SU2
The background color of a pop-up window continues to show an alarm condition after the alarm has cleared from the system. SU3
When a Location's View Trend pop-up window is opened, the pop-up displays the Location temperature in degrees Celsius, also when the temperature unit is set as Fahrenheit. SU2
Zero integer values are displayed incorrectly in the viewLinc dashboard. SU3
When using viewLinc with Internet Explorer 11, a data logger swap cannot be completed successfully. Using a different browser (for example, Chrome or Edge) resolves the issue. SU3

The communication properties (such as IP address or Port and Unit ID) for Modbus devices are not shown in the Edit device properties window if the device was added to viewLinc before viewLinc 5.1 SU3.

Workaround: After an upgrade to 5.1 SU3, the properties data displays correctly once it has been re-entered manually and saved.

SU5
When adding or editing a user in the Users and Groups menu, the Windows authentication method Domain name entry field only accepts alphabetic characters. SU5
Reports When a Location History Report is generated, the graph presentation in the report may display the threshold lines and threshold line colors incorrectly. SU3

When multiple alarm thresholds within the same alarm template (for example, High and High-High) are active for a Location or multiple Locations, pausing the alarm and entering a comment with non-ASCII characters in an acknowledgment comment causes report generation failure for a report that includes this commented acknowledgment.

Workaround: Contact Vaisala Service for support options.

 SU5

When logged in to viewLinc using either the Chinese or Japanese interface language option, reports for a chosen Location cannot be saved if one of the Axis limits of the report has its scaling set to Auto.

The issue can be resolved by using one of the following workarounds.

Workaround 1: Save the report when logged in using a non-Asian language.

Workaround 2: Instead of using Auto scaling, set numeric values for the low and high scale ranges.

Workaround 3: Contact Vaisala Service for a hotfix that can be installed.

 SU5
Certificates

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.

 Version 5.2
Other In viewLinc 5.1 User Guide (M212315), "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). Revision D
The information in user documentation related to the Manage Reports right is incorrect. It should state that if a non-administrator user is granted the Manage Reports right, the user can manage all reports in the system, including the possibility to delete reports. Without the Manage Reports right, a user can only manage reports the user owns, or reports that are owned by a group the user belongs to. Revision C (SU4)
If viewLinc is offline or not connected to the SMS modem, which is operating at the time, incoming text messages will be stored in the modem’s memory. The stored messages are not being processed when viewLinc comes online again. Incoming messages can interrupt outgoing messages. SU8
In some cases, the SMS modem stops sending SMS alerts because the COM port isn't being released by viewLinc. This issue can be resolved using the following workaround:
Workaround:
  1. Change the SMS port number to a different number and save.
  2. Change the SMS port number to its original setting and save.
Version 5.2

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