SUMMARY

Current AVEVA Partners (OEMs or System Integrators) with Consignment Licenses and an active support agreement for AVEVA Edge development are eligible also for consignment licenses to InduSoft Web Studio (IWS) development.  The consignment must be purchased (renewed) on a yearly basis, so the licenses can be re-issued (renewed).

Notice that AVEVA Edge will be the continuing brand name and version for InduSoft Web Studio going forward.  Any version newer than 2020R2 is available only under the AVEVA Edge brand name (not under the InduSoft Web Studio brand name).  Moreover, any projects previously created in InduSoft Web Studio versions are automatically supported by newer versions of AVEVA Edge.  However, projects created in AVEVA Edge are NOT supported in InduSoft Web Studio.

If you are attempting to activate AVEVA EDGE branded software (not IWS), please follow the instructions found in ISS Tech Note 112 instead.

Consignment Licenses are “Development Only” licenses.  Runtime licenses must be purchased separately and CANNOT be requested using this Tech Note.

APPLIES TO

• Development Studio Consignment
• Advanced Development Studio Consignment
• InTouch Dev Subscription 3K Consignment

BEFORE ATTEMPTING THIS PROCEDURE, YOU MUST BE REGISTERED AND CONFIRMED as either an “OEM” or “System Integrator” user with AVEVA thru the technical support website: https://om.AVEVA.com/softwarewebID/

PROCEDURE

1. Install InduSoft Web Studio on the development computer running a supported version of Windows Destkop/Server (e.g.: Windows 10)
2. Close InduSoft Web Studio (make sure that the process “Studio Manager.exe” is not running)
3. Run the “Register” module (Windows button > “Register”)
   

   

4. Select “Softkey > Check > Change License”
5. Select a Network Adapter that most likely will not be removed and does not have a dynamic MAC Address (avoid VPN and virtual adapters).
   

   

6. Copy the “Site Code”.
7. Send an email to edge.license@aveva.com, including the following information:
   • • Subject: AVEVA Edge/IWS Consignment License Request
     • Partner company name: <provide your account name>
     • Partner name: <provide name and email address of the contact registered at the AVEVA Support website >
     • Site Code: Copied from IWS in the previous step
8. If the requested information is verified by AVEVA’s team, then a license Site Key is sent back to the requester.
9. Copy/paste or type the code from AVEVA’s reply email into the “Site Key” field and then click “Authorize”.
   

   

10. Once accepted, a confirmation message is displayed (“Site Key Accepted”) and the new license settings are saved on the computer.  You may now begin using Indusoft Web Studio.

• • If the new “Site Key” is not validated, an error message is displayed. If this happens, double-check that you have entered the “Site Key” correctly. If you still get an error message, visit the technical support page to contact our technical support department.

The consignment licenses for IWS are temporary Softkey licenses, which expire when the current consignment agreement expires (up to one year). When/if the consignment license agreement is renewed by the partner, they can activate the consignment license again.

SUMMARY

Current AVEVA Partners (OEMs or System Integrators) who already own or purchase the following consignment licenses (and support) are also eligible to acquire AVEVA Edge development licenses on consignment for no additional charge.  The consignment must be purchased (renewed) on a yearly basis, so the licenses can be re-issued (renewed).

Notice that AVEVA Edge is the new brand name and version for InduSoft Web Studio.  Moreover, projects previously created in InduSoft Web Studio are automatically supported by newer versions of AVEVA Edge.  However, projects created in AVEVA Edge are NOT supported in InduSoft Web Studio.

If you are attempting to activate InduSoft branded software (not available after version 2020R2), please follow the instructions detailed in ISS Tech Note 113 instead.

APPLIES TO

• Development Studio Consignment
• Advanced Development Studio Consignment
• InTouch Dev Subscription 3K Consignment

BEFORE ATTEMPTING THIS PROCEDURE, YOU MUST BE REGISTERED AND CONFIRMED as either an “OEM” or “System Integrator” user with AVEVA thru the technical support website: https://om.AVEVA.com/softwarewebID/

Consignment Licenses are “Development Only” licenses.  Runtime licenses must be purchased separately and CANNOT be requested as Consignment using this Tech Note.

PROCEDURE

The instructions to activate a consignment license for AVEVA Edge are available at https://sw.AVEVA.com/support/intouch-hmi-activation, and described below in further details:

1)  Install AVEVA Edge software on the development computer running a supported version of Windows Desktop/Server (e.g.: Windows 10).  [Software downloads are available here.]

2)  Close AVEVA Edge (make sure that the process “Studio Manager.exe” is not running)

3)  Run the “Register” module (Start > AVEVA Edge > “AVEVA Edge Register”)

4)  Select “Softkey > Check > Change License”

5)  Select a Network Adapter that most likely will not be removed and does not have a dynamic MAC Address (avoid VPN and virtual
adapters)

6)  Copy the “Hardware Identifier”

7)  Visit the AVEVA website (https://softwareom.wonderware.com/Licensegen/default.aspx) to activate the license.  You need your Wonderware credentials to log in to the site. If you are eligible to consignment licenses, you will be prompted with two options: “End User Runtime Licenses” and “Consignment”. Select “Consignment” and click on the “Submit” button to activate Consignment Licenses.

The “End User Runtime License” option must be selected for perpetual licenses only (not consignment). When selecting “End User Runtime License”, the system will ask for the Serial Number of the purchased license. It is not necessary to enter any Serial Number to activate consignment licenses.

Note: If you are NOT able to log-in to this site, or do NOT get the “Consignment” option, either your registration has not been confirmed by AVEVA, or, you are NOT eligible for consignment licenses. In order to be eligible, you must be registered correctly as a Partner with AVEVA (not End User) and own at least one of the consignment licenses mentioned above in the Abstract with an active (not expired) support agreement.

• To check your registration, please contact AVEVA at TechMaster@aveva.com.
• To establish an active consignment agreement, please contact your Sales Representative, or sales@industrial-software.com.

8)  Select the consignment license for the version of AVEVA Edge that you want to license, paste the “Hardware Identifier” from the “Register” module into the web form and click submit.

9)  If a valid “Hardware Identifier” has been entered, then a license “Activation Code” is returned. Copy/paste or type the code in the “Activation Code” field in the “Register” module, and then click Authorize.

10) The new license settings are saved on the computer and a confirmation message is displayed (“Activation Code Accepted”).

• If the new “Activation Code” is not validated, an error message is displayed. If this happens, double-check that you have entered the “Activation Code” correctly. If you still get an error message, contact our technical support department.

The consignment licenses for AVEVA Edge are temporary Softkey licenses, which expire when the current consignment agreement expires (up to one year). When/if the consignment license agreement is renewed by the partner, they can activate the consignment license again.

Option A

For ArchestrA Licenses (InTouch v2012/Historian v 10.0 through v2014 R2 SP1)

SUMMARY

If you receive an error message(s) stating that the “IDE requires a network connection to continue…” or “A local network connection could not be found…” when launching the AVEVA System Platform IDE or attempting to open an AVEVA InTouch managed application within a galaxy, it is recommended you install Microsoft’s KM-TEST Loopback Network Adapter.

AVEVA Application Server uses the SuiteLink protocol (a proprietary TCP/IP wrapper) and the NMX protocol (Network Message Exchange) to communicate with I/O devices and platforms/objects in the application galaxy. The System Platform Integrated Development Environment (IDE) uses the NMX protocol to communicate with and deploy objects to platforms in the galaxy (this requires a valid network connection for development and testing operations). In the absence of a network adapter or valid network connection, Microsoft’s Loopback Adapter may be installed to satisfy the System Platform IDE’s requirement for a valid network connection.

The Microsoft KM-TEST Loopback Adapter will prevent the System Platform IDE from closing in the event the development computer is using a wireless network connection that has intermittent connectivity losses.

APPLIES TO

• Application Server v3.1 and newer
• Windows Vista, 7, 8, 10, Server 2008, or Server 2012

PROCEDURE

Note: The following example uses Microsoft Windows 10 operating system.

1. Click Start, then type hdwwiz.exe in the search box.

2. The hdwwiz command appears. Choose the option to “Run as Administrator”

3. The “Add Hardware” wizard appears. Click Next.

4. Select “Install the hardware that I manually select from a list (Advanced)”, then click Next.

5. Select Network adapters, then click Next.

6. Select Microsoft as the “Manufacturer”, and then select Microsoft KM-TEST Loopback Adapter as the model, then click Next.

7. Select Next to confirm the installation.

8. Select Finish to complete the installation.

9. Confirm that the Microsoft KM-TEST Loopback Adapter appears in Network Connections.

Applies to

• Microsoft Windows Operating System

Abstract

Determining the cause of system failures especially application crashes can be difficult to pinpoint. Using the Windows Administrative snap-in Performance utility, it is possible to create a graphical representation of the state of the system at a given period of time. The resulting files can be provided to your support provider for analysis.

Procedure

1. Open the Performance snap-in using one of two methods:

• from the Run line: Start > Run… : type in “Perfmon“, or
• from the Control Panel: Start > Control Panel > Administrative Tools > Performance

Next, expand the Performance Logs and Alerts section and select Counter Logs.

2. Right click Counter Logs and select New Log Settings…

3. Give the log a useful name.

4. In the Log Settings screen, you will need to add Objects (collections of counters) or individual Counters. For this sample log choose Add Objects…

5. Make sure to select Use local computer counter objects. Then scroll down in the list to choose the following Objects to log:

• Memory
• Process
• Processor
• Thread

Click Close button when finished.

6. You should have the following Objects selected for your log. By default the log file will be saved in the C:\PerfLogs folder.

7. If you select OK, the system may generate an error if the C:\PerfLogs folder does not already exist. Select Yes to allow the system to create it.
Alternatively, you can select the specifics about the Log File format and location on the Log Files tab of the Log Properties screen.

8. Once you select OK, the log will immediately start, and it’s icon will be displayed as green for active or red for inactive.

9. To stop the log from logging to the file, right click the counter log and select Stop.

10. Next, locate the log file and send the resulting .blg file to support provider.

Note:
The above steps can result in very large log files due to the number of counters contained in the four Objects selected. This should be closely monitored to ensure that the log files are not growing at too high a rate to compromise the hard drive’s available space. Ideally, this would run until the target problem behavior occurs (i.e. application crash) at which time the logs can be retrieved and sent to support.

SUMMARY

The ArchestrA Log Viewer (Found in the System Platform Management Console aka SMC) has the ability to add or remove additional logging components, which can be very useful for troubleshooting.

APPLIES TO:

·       System Platform Management Console

PROCEDURE

1. Open the System Platform Management Console (Start > AVEVA > System Platform Management Console)

2. Expand the Log Viewer → Default Group → Local. Right-Click Local à Log Flags…

3. The Log Flag Editor will open in a separate window.

4. For this example we will enable the ArchestrASymbolProvider Trace flag. From the list on the left choose ArchestrASymbolProvider, and on the top right under the Log Flags for ArchestrASymbolProvider make sure the Trace flag is checked.

5. Next click the File > Apply button on the menu bar.

6. A dialog box will appear confirming your selection.

Select Yes and a confirmation dialog box will appear. Click OK.

7. In the ArchestrA Log Viewer in the System Platform Management Console the new log flag will appear once the selected object, ArchestrASymbolProvider Trace, in this instance has new information to post to the log.

NOTE: Please remember to disable log flags after finishing troubleshooting.

SUMMARY

This Tech Note describes a procedure for configuring automatic logon for InTouch application and in Windows.

APPLIES TO

• AVEVA InTouch HMI

PROCEDURE

Configuring Automatic InTouch Application Startup

1. Start the InTouch HMI Application Manager, select the Application you would like to start automatically and from the Tools menu select Node Properties.

2. On the Node Properties window, place a check in the “Start WindowViewer as a service” checkbox.

3. Set up your OI-Server(s) to “Auto start after reboot”.

4. Ensure the connection between InTouch and OI-Server

To ensure InTouch keeps trying to establish connection with the I/O server, open InTouch WindowMaker for the application and go to Special | Configure | WindowViewer

Change the ‘Retry Initiates’ setting from 0 to 5 sec (for example) on the ‘WindowViewer Properties’ screen. This setting means that should the connection between InTouch and the I/O server go down, InTouch will try re-connecting to I/O Server every 5 seconds.

5. Reboot the computer and the application will startup automatically.

Setting automatic logon in Windows

If you want to also configure automatic logon, you can follow the steps provided by Microsoft: https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon

SUMMARY

It may be necessary to view the version of Microsoft .NET Framework currently being used by your system.

APPLIES TO

• Microsoft .NET Framework

PROCEDURE

1. First access the registry editor by searching “regedit”

2. Within the registry editor locate and expand the “NDP” key at (HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP). The “version” child key of “NDP” will display the version of .NET Framework currently in use. The specific subkey is determined by the version (For this tech note we use v4 which shows the version in either in Client or Full).

For more information on Microsoft .NET Framework versions and dependencies, you can visit: https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies

SUMMARY

It may be necessary to view the Windows Event Log file when troubleshooting AVEVA products. The Windows Event Log file may contain information useful for troubleshooting common issues. An export of these logs may be requested by a technical support specialist.

APPLIES TO

• All AVEVA products
• Windows Event Log

PROCEDURE

1. First, access Computer Management and expand Event Viewer

2. Expand Windows Logs. Right-click on the desired Event Viewer log and select “Save All Events As…”

3. Browse to the location where you plan to save the file. Name the file with an .evt extension. Select “Save.”