General Notes - viewLinc 5.0

viewLinc 5.0.x Errata

Document code
viewLinc 5.0
Document type

The Errata provides additional information about viewLinc 5.0 product functionality, a description of known issues, and issues that have been fixed with Service Updates. For current system specifications, see Vaisala viewLinc 5.0 Datasheet B211708EN.

Important Notices

  • If you add an AP10 access point with firmware version 5.0 (the current shipping version), you must update the firmware of all AP10s at the site to version 5.0 as well. If all AP10s do not have the same firmware, it could result in radio interference and negatively affect the proper operation of the viewLinc system.
  • Between October 1, 2022 and January 31, 2023 Microsoft is removing the ability to use Basic authentication in Office365 email services. If you are currently using Office365 for viewLinc email notifications, verify that Basic authentication over Authenticated SMTP remains enabled in your Office365 account to ensure that notifications can still be sent. Once Microsoft disables Basic authentication, viewLinc will be unable to receive alarm acknowledgments via email.
  • viewLinc 5.0 uses TLS 1.0 for communication with email servers. TLS 1.0 is currently being deprecated in many email servers, which causes issues in viewLinc 5.0 email functionalities.
    CAUTION TLS 1.0 deprecation prevents viewLinc 5.0 from sending emails to servers that no longer support TLS 1.0. Vaisala recommends updating from viewLinc 5.0 to viewLinc 5.1.

Upgrade Notes

CAUTION Always back up application data before upgrading.
  • viewLinc uses a certificate and security key to establish a secure connection between network PCs and the viewLinc Enterprise Server. Vaisala recommends using a trusted certificate - either from your company's domain certificate authority or a 3rd party. If your system uses a self-signed security certificate you may see a certificate error. To prevent a certificate error message from appearing, set each user's browser to trust the certificate. Replacing the self-signed certificate with a trusted certificate automatically prevents certificate errors from appearing.
  • To ensure data timestamp accuracy, verify that the viewLinc Enterprise Server time is set accurately before installing the viewLinc software.
  • Only 64-bit Windows Operating Systems are supported.
  • Alarm Notification Send To fields are limited to viewLinc users and groups. To retain existing non-viewLinc email addresses, save them by creating viewLinc user profiles prior to upgrade.
  • Deactivated Private Threshold Settings are not upgraded. To preserve deactivated settings, reactivate them prior to upgrade.
  • If communication is interrupted during an upgrade, restart the Enterprise Server (ES) machine after all device hosts are upgraded. If communication does not resume after ES restart, manually enter the ES IP address in the “server_name” entry in the [remote_host] section of the device host config file (Public Documents\Vaisala\Vaisala viewLinc\config\viewLinc.cfg), then restart the viewLinc Device Host Service.
  • Transfers functionality is no longer supported.
  • Views created in earlier version are visible to all users on upgrade.
  • Manage Reports right is required to assign report ownership.
  • All users are automatically assigned to the Everyone group, which has Manage Events right.
  • Installation directory paths have changed. If you use SetPoeRelay batch files to initiate commands: copy the batch file from the old directory path (C:\Program Files (x86)\Vaisala\Vaisala Veriteq viewLinc\...) to the new directory path (C:\Program Files\Vaisala\Vaisala viewLinc\...), update the path inside the batch file to reflect the new installation path, and then update all command notification templates that reference the batch file location.
  • For a complete list of all feature changes, see viewLinc User Guide, “What’s New for Upgrade Users”.


  • There is an issue affecting viewLinc between versions 5.0 and 5.1.2, when device hosts are used. The Host and CA certificates have expired in these versions. This affects connectivity between the Enterprise server and Device Hosts and will interrupt data collection and alarming. Contact Helpdesk for updated certificates. (Versions 5.1.3 and newer are unaffected).
  • Typical average update periods based on system size: Small, 1 minute / 10 users; Medium, 3 minutes / 20 users; Large, 6 minutes / 50 users.
  • Email format uses RFC-2047 encoding.
  • Events triggered by changes to the Windows OS clock cannot be disabled.
  • SMS messages can be unlimited in length if your cellular network supports it, otherwise they are limited to 70 characters.
  • Attachments sent by email may arrive as .dat files, depending on the email server type. To open a .dat file, first save the file as .pdf.
  • Custom email/SMS messages created in a specific language are only available to users with the same language preference set in their user profile.
  • Alarm and notification delays are limited to 23 hours and 59 minutes.
  • Server scan time on a fresh installation takes longer during the initial backfill period.
  • Duplicate "viewLinc Restarted" email and SMS notifications are received when services are restarted from within viewLinc.


  • When a user pauses alarming on a Location, all existing alarms in that Location are auto-acknowledged and turned off.
  • There may be a delay in refreshing the active alarm list of a time equivalent to the System Update Duration.
  • If a user is configured to receive audible alarms, an alarm sound is only heard when the user logs in. Alarms that commence while the user is already logged in do not trigger an audible alarm sound.

Data Loggers

  • During a data logger swap, device alarm settings are automatically copied to the new data logger.
  • When swapping data loggers, it is important to allow the new data logger to come to equilibrium before placing it on the port to ensure that data recorded from outside of the environment is not included on reports.
  • To prevent Location threshold alarming after a swap, either clear the data logger before swapping it back into viewLinc, or wait for the automatic backfill to complete (wait 5-10mins for DL data loggers; force 4 beacons for HMT140; wait up to 12+hours for RFLs) before linking the channel to the Location.
  • RFL Data Loggers:
    • When swapping a probe on an RFL connected to viewLinc, make sure the new probe has the same number of channels, channel types.
    • Before a probe swap, make sure viewLinc is communicating with the RFL data logger and all backfills are complete (do not power off the RFL).
  • DL Data Loggers:
    • Before removing a probe on a DL data logger, deactivate the data logger to prevent a configuration alarm.
  • HMT140 Series Data Loggers:
    • If you use NIC-teaming redundancy products, HMT140 data loggers require a dedicated Network Interface Card (NIC) and IP address to avoid communication interruptions.
    • HMT140 data loggers can have a device-specific password. If there are multiple HMT140 loggers with different device-specific passwords connected to viewLinc, bulk change actions to all connected HMT140 loggers simultaneously are not possible.

300-Series Transmitters

  • The Firmware version must be 5.04 or later.
  • Upgrade to Firmware version 5.10 where it is possible (please contact Vaisala Technical Support if you require assistance).
  • 300-series transmitters without LOGGER-1 modules do not support the historical data backup retrieval and data restoration process.
  • If 300-series transmitters are configured with timeouts greater than the viewLinc scan period, brief configuration alarms may occur.


  • Manually generated and scheduled reports are processed in a queue displayed in the Reports Progress window, in the Progress column. Since non-admin users can only see the progress of their own reports, the Progress column may update periodically to indicate a change in the queue sequence of the report, in relation to all other reports in the queue. This could be a significant period of time depending on the size and quantity of reports already in the queue.
  • To resolve issues exporting to Excel, remove double quotes (“) entered in a device’s Unit field (use device-specific software to modify the Unit field).
  • When downloading reports using an IE browser, non-ASCII file names may not display correctly.
  • System report has no default content. The report cannot be saved until some content is selected.
  • To prevent a previously generated interval statistics table and/or graph from appearing on a Location History report, save the report without the Show graph option selected.


  • The viewLinc POS Terminal Service is available, but POS terminal hardware is no longer available from Vaisala. POS terminal functionality is replaced with viewLinc Remote Display (http://<viewLincIPaddress>/display).
  • POS terminals show alarms when alarms are detected, even if an alarm activation delay is set.

UI functionality

  • The Events Location filter does not identify all Location-related events generated when editing the Locations Manager tree. To filter these events, use the text filter.
  • A Chrome browser is recommended for remote display terminals.
  • In Views Manager, avoid creating views when a search filter is active.
  • The European number format (decimal separator) may display incorrectly in some parts of the UI.

Mobile UI functionality

  • Mobile UI updates are performed on a timer basis and not via server push messages.

  • Mobile UI does not reflect changes in the Locations tree structure. Refresh the Locations panel to view the latest changes.

  • When the mobile keyboard is visible, orientation changes may cause rendering problems.

  • When a Trend is opened on a mobile device for the first time it may be blank.

  • The RH unit may not display correctly in pop-up on the iOS Safari.

  • The Trend window opens directly if opened from a previously created bookmark.

  • The confirm identity pop-up may not appear completely on the mobile screen.

  • The option, "Pause device alarming", only applies when selecting individual Locations.


  • The viewLinc API user document shows the login URL as:


    It should read as: https://nnn.nnn.nnn.nnn:443/__login__/noui?username=xxxx&password=yyyy.