InTouch HMI resolved issues
- Last UpdatedSep 24, 2026
- 6 minute read
InTouch HMI 2023 R2 SP2 includes corrections for the issues listed in the following table. These issues are listed by their Defect ID, its assigned Service Request (SR) or Case Number, and a brief description of the issue.
|
Defect ID |
SR/Case Number |
Description |
|
1521821 |
960113182 |
InTouch HMI allocated View.exe to individual CPU cores in a Remote Desktop Services (RDS) environment. |
|
4037951 |
960637314 |
The snapshot approach for the alarm list could not retrieve alarms when querying the Alarm Hot Backup Pair. |
|
4074215 |
960610836 |
The managed InTouch application was temporarily not responsive when the GR node was shutdown. |
|
4316494 |
962613740 |
After minimizing and then maximizing the WindowMaker window, focus within the application was lost. The Enter key did not activate the selected object, and the application became unresponsive during minimize operations. |
|
4370864 |
962641284 |
After migrating a Galaxy from System Platform 2014, the OCMC frequently logged the error "Column does not exist". |
|
4379938 |
962644999 |
When Network Application Development (NAD) was enabled, UDTs were missing on a French Operating System. |
|
4384789 |
962651595 |
An error was encountered when writing timestamps with a non-zero third millisecond digit in the SQL DataGrid Application. |
|
4413338 |
962651493 |
At runtime, frame windows with InteractionMode set to None did not behave correctly during touch interactions. |
|
4416282 |
962651617 |
When switching language, Value Display with Truth Table did not display properly in frame windows. |
|
4429632 |
962678524 |
An issue occurred while data was written from the InTouch Web Client, during which warnings related to aaServicesMXDataService were observed. |
|
4429717 |
962691563 |
A single click in the UDT property dropdown area selected the first item in the list. |
|
4437562 |
962667642 |
Domain accounts were not granted the expected permissions when logging into the InTouch application. Upon login, the user access level remained at 0. |
|
4439606 |
962684788 |
After migrating a Galaxy from System Platform 2020 R2 to System Platform 2023 R2 SP1 P03 or System Platform 2023 R2 SP1 P04, security-controlled popup animations did not update correctly, and graphic custom properties were not consistently refreshed. |
|
4443292 |
962670414 |
After hotfix 4349946 was installed, the Alarm Client Control for InTouch HMI and OMI was corrupted, which caused the application to stop responding. |
|
4459708 |
962702121 |
After upgrading from InTouch HMI 2023 R2 SP1 P02 to InTouch HMI 2023 R2 SP1 P03 or System Platform 2023 R2 SP1 P04, some UDT instance properties were incorrect. |
|
4497297 |
962703741 |
The Alarm Client Control displayed alarm timestamps in PST when the client time zone was set to Perth (+08:00) until an alarm entry was selected, after which the timestamps were corrected to Perth time. |
|
4513808 |
962727458 |
Alarm Client Control was unresponsive when the All System Alarms filter was applied. |
|
4518705 |
962729521 |
WindowViewer became stuck on exit when WWControl(InfoAppTitle("View"),"Close"); was called. |
|
4519748 |
962706218 |
After migrating the application from InTouch HMI 2020 R2 SP1 to InTouch HMI 2023 R2 SP1 P03, an error stating "WM /Unknown opcode in OperandProcessDbNames0: 0, pPExp:800702BD" occurred when the application was launched. |
|
4528677 |
962722274 |
The InTouch application stopped responding intermittently during alarm acknowledgment in InTouch HMI 2023 R2 SP1 P01 or later. |
|
4542543 |
962740639 |
In InTouch HMI 2023 R2 SP1 P03 or System Platform 2023 R2 SP1 P04, when Network Application Development (NAD) was temporarily set to None and later enabled, the Local Working Directory was reset to the default path instead of retaining the previously saved custom path. |
|
4545254 |
962697134 |
LGH files larger than 2 GB failed to display historical data in Trend controls and caused high CPU usage. |
|
4548076 |
962714694 |
InTouch Web did not display graphics correctly when Owning Object was configured on a UDT in a managed InTouch application. |
|
4552217 |
962748012 |
In InTouch HMI 2020 R2 SP1 or later, CPU usage for view.exe increased to nearly 100% after approximately 20 minutes when viewing a screen with the Trend Client Control. |
|
4562175 |
962746550 |
In System Platform 2023 R2 SP1 P04, leading zeros were removed from the String Custom Property. |
|
4641780 |
962705600 |
After migrating the project from version InTouch HMI 2014 R2 SP1 to InTouch HMI 2023 R2 SP1 P02 or later, the alarm filter syntax was not interpreted the same way as in version InTouch HMI 2014 R2 SP1. |
|
4642598 |
962759453 |
The input-enabled textbox used to modify a value was always shown on the primary screen, even when the popup graphic displaying the value was on another screen. This issue occurred with all input-enabled text fields. |
|
4652375 |
962754809 |
After upgrading to System Platform 2023 R2 SP1 P04, the ShowGraphic() function did not work on OMI MapApp. |
|
4665314 |
962749965 |
Trend Pen, when hosted in InTouch Web Client, did not retrieve the historical data from LGH files. |
|
4680522 |
962740017 |
After configuring User Authentication and using the Sign Out button to close the session, the lock on free access to the InTouch Web Client still persisted, preventing access from another session. |
|
4683144 |
962752725 |
Selecting a row in the DataGrid cleared the displayed data when a custom property was configured for the Selected Row property. |
|
4692757 |
962786588 |
After migrating to System Platform 2023 R2 SP1 P04, MapApp using offline maps with an XYZ source stopped working when any XYZ source was defined. |
|
4730773 |
962706218 |
After migrating a managed InTouch application from System Platform 2017 to System Platform 2023 R2 SP1 P03, the InTouch script counts were displayed incorrectly. |
|
4748053 |
962815899 |
A new public property on the Alarm Viewer control was exposed to provide percent complete information. |
|
4760099 |
962817719 |
Error messages in Chinese were logged from the SymbolProvider component. |
|
4766947 |
962823074 |
The Industrial Graphic object using exponential notation displayed values with incorrect rounding when the values were greater than tens. |
|
4769057 |
962805437 |
When navigating around and then opening Cross Reference, a "Not enough memory for window" error message appeared in the OCMC. |
|
4776916 |
962824357 |
The View stopped responding when a user logged in with the login window. |
|
4780397 |
962817049 |
Strange behavior occurred when deploying the InTouch application with "override WindowViewer default configuration". |
|
4786454 |
962828457 |
After upgrading the application from InTouch HMI 2020 to InTouch HMI 2023 R2 SP1 P04, the GetEUDesc() functionality to retrieve the engineering unit description did not work. |
|
4793706 |
962834358 |
The Trend Pen graphic either failed to plot the trend or took a very long time to plot the trend. |
|
4827767 |
962848713 |
In System Platform 2023 R2 SP1 P04 Chinese version, a normal application of Purge/Archive and Activate displayed the error: "User has no permission to run alarm Purge/Archive as a Windows service." |
|
4828672 |
962834982 |
After migrating the Galaxy from version System Platform 2014 to System Platform 2023 R2 P01, owning object function did not work correctly for grouped objects. |
|
4832577 |
962849130 |
The presence of a frame window caused smart symbol template corruption. |
|
4847688 |
962854828 |
After installing hotfix 4779989 on a Japanese machine, WindowMaker stopped responding. |
|
4878558 |
962859511 |
After migrating the InTouch application to the new version, when loading QuickFunctions with larger scripts into the WindowMaker editor, InTouch WindowMaker became unresponsive. |
|
4889918 |
962874271 |
When a trend popup was opened, the View.exe (WindowViewer) process consumed a significant number of USER and GDI handles . When these popups were closed using HideSelf(), the handles were not released, causing the handle count to reach the Windows USER/GDI limit. |
|
4908656 |
962879544 |
WindowViewer toolbar was positioned incorrectly after RDP disconnect/reconnect with AlwaysMaximize=1. |
|
4910346 |
962859868 |
After migrating the InTouch application from System Platform 2020 R2 SP1 to System Platform 2023 R2 SP1 P04, copying (or duplicating) and pasting an Industrial Graphics Numeric Display within the same window caused the object to become smaller. |
|
4910367 |
962877576 |
When historical alarms were queried from SQL server, alarms that had an alarm duration without milliseconds displayed '00:' in the Alarm Client Control. |
|
4913073 |
962867008 |
The .exe created by the InTouch Application Publisher utility, when executed, caused the InTouch Application Expander to stop responding and required manual closure. |
|
4939438 |
962892328 |
An alarm was triggered from the object and a record for UNACK_ALM was created in the WWALMDB Alarm Details table. However, when the alarm was acknowledged and returned to a normal state, the ACK_ALM and ACK_RTN records were not created in the Alarm Details. |
|
4571993 / 4400295 / 4503020 |
960642628 |
When notifying clients, WindowMaker was not able to update the appchng.fsm file once the file existed. Network Application Development (NAD) clients were not notified. |
|
4852329/4788355 |
962827617 |
After migrating from System Platform 2017 to System Platform 2023, there was a different background appearance between WindowViewer and the InTouch Web Client. |