AVEVA OMI Issues

Issue Number

Description

IMS 1212168

On Windows 10 operating systems, layouts created in System Platform 2020 with non-English OS/regional settings show a warning and do not open when migrated to System Platform 2020 R2 or 2020 R2 SP1.

Workaround: Before migrating the galaxy, make sure the operating system locale is set appropriately by following these steps:

1. Open the Windows Control Panel and select Region.

2. Select the Administration tab when the Region popup opens. The Administration tab contains two buttons:

   • Copy settings

   • Change system locale

3. Select Copy settings and then mark the checkboxes to copy current settings to "Welcome screen and system accounts," and "New user accounts."

4. Select Change system locale and then choose the applicable locale from the dropdown list.

TFS 1369154

Under certain circumstances, an instance derived from a template with an invalid reference will not show a warning during design time. This can occur if the following occurs:

1. A symbol is added to the Graphic Toolbox with an undefined relative reference, for example, “Me.Attribute001,” where Attribute001 has not been created yet.

2. The symbol is then added to a layout.

3. The layout is linked to a UDO (User Defined Object) template. When the template is saved, no warning is displayed.

4. When an asset is derived from the template, no warning is displayed for the instance either.

Result: Although no warnings are issued during design time, when you create and then deploy a ViewApp with the linked layout, and show the linked layout in any screen, an error message will be displayed at run time (or in Preview Mode) that will allow you to troubleshoot and correct the error. The message will be similar to:

Element ‘TEXT1’ in Symbol ‘UDO_001.S1’ has Configuration error: Invalid reference ‘Galaxy1:Me.Attribute001’ with owning object ‘UDO_001’ does not exist.

TFS 1160616

If an admin user logs in, launches a ViewApp, and then logs off the system while leaving the ViewApp running, registry keys are unloaded in the profile of the user account. This results in continuous errors from CheckPointFileServer in the logger similar to: ""INVALID HRESULT LINE765 File CheckPointFile.cpp hResult 80003fa after logging off and logging on as different users (non-admin)."

Cause: This is a known Microsoft issue. This problem typically occurs after an administrator uses a service account to log in to the server for an interactive session, and then logs off. For example, an administrator may log in to a Web Front End (WFE) server by using the farm account, and then log off. This activity forces the registry keys to be unloaded in the profile of that account, and makes the keys unavailable for future use. Microsoft recommends using either of the following workarounds to resolve this issue. For more information, see:

"800703fa Illegal operation attempted on a registry key" error

A COM+ application may stop working on Windows Server 2008 when the identity user logs off

Workaround 1: Do not log in to the server for interactive sessions by using a service account.

Workaround 2: Disable the related Windows User Profile Service feature as follows:

1. Open the Group Policy editor (Gpedit.msc) on the affected server.

2. Open the User Profiles folder in the following path:

Computer Configuration > Administrative Templates > System > User Profiles

3. Locate the "Do not forcefully unload the user registry at user logoff" setting.

4. Change the setting to Enabled.

CR L00150114

SR59513303: TheGetCPTimeStamp() scripting method, when used in an AVEVA OMI action or named script within a symbol, does not return the timestamp at run time. Instead, it returns characters for the timestamp format, such as "mm/dd/yyyy hh:mm:ss." No errors or warnings will appear in the logger. This is similar to issue 777504, listed below.

Workaround: Use the GetCPTimeStamp() method in an object script instead of a symbol script.

TFS 1100582

Switching languages during run time while using multi-content panes that use locale-specific scripting calls can sometimes result in errors in the logger.

Workaround: Restart the ViewApp after switching the run-time language. This action fully resolves the issue with no loss of functionality.

Missing NavTree

After upgrading or migrating an AVEVA OMI ViewApp from 2017, a warning message states that the NavTree entity could not be found. In 2017 Update 1, this navigation object has changed and is now called “NavTreeControl.”

Workaround 1: To replace the NavTree object in a ViewApp or Layout when upgrading from System Platform 2017:

1. Open the ViewApp or Layout that shows the warning.

2. In the ViewApp or Layout editor, look in the Actions list for all references to “NavTree.” An icon showing “Content not available” will be displayed for these references.

3. To see the entire action list for a ViewApp, toggle the Actions for Primary switch to show Actions for Home (does not apply to the Layout editor).

a. Replace the NavTree object with the new NavTreeControl.

b. Search for NavTreeControl under the Toolbox tab.

4. Drag the NavTreeControl onto the pane to replace the NavTree.

5. Confirm that you want to replace the content, then save the ViewApp or Layout and close the editor.

6. Verify Layouts and ViewApps no longer show any warnings related to the NavTree.

7. Deploy the ViewApp.

Workaround 2: To replace references to NavTree when importing packages from System Platform 2017:

5. Launch the IDE and open the “Find” dialog.

6. Search for “NavTree” using the default search settings.

   If the package file contains the obsolete NavTree object, it will be listed in the search results.

7. Double-click the NavTree search result, which will select the NavTree object in the Graphic Toolbox.

8. Delete the NavTree object from the Graphic Toolbox.

9. Use Workaround 1 to replace the NavTree object with the new NavTreeControl object.

TFS 774717

When an AVEVA OMI application (View.exe) that uses one of the following web controls is run in 4K mode or on multiple 1080p monitors, under certain circumstances the application may stop responding:

• InSightApp

• MapApp

• WWWebAppControls

Workaround: When running a ViewApp that uses a web control on a 4K monitor, set the monitor resolution to 2560 x1440 or less. When running the ViewApp on 1080p monitors, do not attempt to span multiple monitors.

TFS 777504

The GetCPQuality() scripting method is not supported in AVEVA OMI. If used in a ViewApp, it always returns quality = 0 (bad quality). This is similar to issue L00150114, listed above.

TFS 781006

If an invalid custom property is added to a symbol, no warning is logged in the Operations Control Management Console, even though no value is displayed for the custom property.

TFS 781620

The Height and Width properties of a group with text elements do not change in accordance with changes made to the label font size, and are not rendered correctly.

TFS 784470

Tooltip animations that contain multiple lines of text with line breaks may not display properly in deployed ViewApp.

TFS 784474

A tooltip may partially cover the element with which it is associated in the deployed ViewApp.

TFS 787192

When OSGroup security mode is used, the VerifiedWrite dialog is not displayed when you modify the value of a VerifiedWrite attribute from a combobox, if you first attempted to perform the VerifiedWrite without having the correct security credentials.

TFS 789958

On some high resolution tablet devices, such as the Surface Pro 4, object names in the System Platform IDE may have insufficient line spacing between items, which can make it harder to read object names.

TFS 794383

When a custom property is changed from public to private, the change does not have any affect, and the value of the private custom property is shown at run time (private values should not be shown). Similar situations occur when:

• An override values for a custom property that is later made private. The override is also shown at run time.

• An override is applied to a custom property, and later the custom property is locked (can no longer be overridden). When the ViewApp is redeployed, the override value is still shown.

Workaround: Manually validate the outermost symbol and then deploy the ViewApp.

IMS-1989484

After galaxy migration, if a linked symbol information is unavailable, the layout validator cannot process the linked symbol. This can result in the layout in warning state. Immediately connecting to the galaxy will display a warning state and empty symbol preview for the specific unprocessed linked symbol.

Workaround: After the migration completes, connect to the galaxy and open the layout in warning state. Identify the symbols showing empty previews, validate those symbols only, then validate the layout to resolve the issue. You do not need to validate all symbols, only those symbols with missing previews in the layout.

IMS-1989662

Some alarm field localizations might not appear in the Alarm Control in InTouch HMI and AVEVA OMI when running in Historical Alarms and Events client mode.

When running the Alarm Control, either as an embedded symbol in InTouch HMI or in AVEVA OMI, or as an AlarmApp in AVEVA OMI configured to run in Historical Alarms, Historical Events, or Historical Alarms and Events modes, some alarm field localizations may not load even if present in the galaxy translation files. This occurs when the control is configured to display alarms from the History Blocks database. Following are the known cases (Alarm/Event types) where the localizations fail to load at runtime:

1. For user write operations (User.Write) and events, the AlarmComment field is only partially localized in an Alarm App configured to view Historical Alarms and Events.

2. For a Boolean alarm (Alarm.Set, Alarm.Clear) events, the AlarmComment, Limit and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events,.

3. For Boolean write operations from an I/O reference (Application.Write) events, the AlarmComment and Value field localizations are not displayed in an Alarm App configured to view Historical Alarms and Events.

IMS-1991749

After installing and configuring System Platform 2023 or rebooting the system, the following message will be logged in the Operations Control Logger, "AnnounceOnline could not announce to local discovery service due to communication error," when the InTouchIDataService is unable to connect to the Discovery Service. This can occur if the InTouchIDataService starts before the Local Discovery Service. This message will not be logged after the Discovery Service starts. There is no functional loss once all services have started.