Tech Notes

Tech Note: 151

AVEVA Edge: Viewer module could not connect to the Run-Time

The following error may be encountered on a computer running AVEVA Edge HMI (or Indusoft Web Studio):
The Viewer module could not connect to the Run-Time. Please check if the runtime is running and that you are connecting with a compatible version.

This tech note provides steps to troubleshoot and resolve the issue.

...

Tech Note: 149

Unblocking Downloaded Files in Windows

Windows has a security feature that blocks files downloaded from the internet to protect your system from potentially malicious content. When a file is blocked, it can prevent you from opening or executing it, which can be inconvenient if you know the file is safe. Unblocking the file tells Windows that you trust the source and are allowing it to be used on your computer.

This tech note will guide you through the process of unblocking a downloaded file.

...

Tech Note: 147

How to find the Galaxy Name using a .cab file

When creating a backup of a galaxy (.cab file), the default file name is the name of the galaxy being backed up, but the name can be modified if desired.

If you are maintaining backups of multiple galaxies with modified file names, it can become unclear which backup belongs to which galaxy.  The process below can be used to determine the name of the galaxy used to create the .cab file.

...

Tech Note: 145

Potential Failure in Detecting Certain Alarms

AVEVA has identified an issue with System Platform 2023 and System Platform 2023R2.

AVEVA is releasing hotfixes for each of the affected versions. Details can be found in the table below.  AVEVA strongly recommends that users install the appropriate hotfix as soon as possible.

...

Tech Note: 142

License Server Core Service goes into a STOPPING state and machine must be rebooted in order to recover

The AVEVA Enterprise License Server repeatedly goes into a "Stopping" state.  When this happens, a reboot is required to restore it to Running.  The following message appears in the OCMC logs:

LS Agent can't use the ServiceController API to control the LS. Time out has expired and the operation has not been completed. Stack Trace: at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at LicServer.WindowsService.TrackSELicServer.MonitorLicServer()

This tech note will explain how to regenerate the license server trusted storage files to resolve the issue.

...