24.4.1 Blank popup on login - UC_TELEMETRY_SETTINGS AWI log error
search cancel

24.4.1 Blank popup on login - UC_TELEMETRY_SETTINGS AWI log error

book

Article ID: 429767

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

When logging into the AWI on 24.4.1, a blank popup appears with no words in it.  

No other symptoms appear to be there.  When looking at the AWI logs, the following error appears:

2026-02-10 13:18:08,825 pool-2-thread-1634     [WARN ] AWI_Connection_name:0100/AUTOMIC/AUTOMIC node0ejopd9m1kbxs8y6o1c177mv83-1 0000000001261010 +LOAD 7583 [com.uc4.ecc.plugins.telemetry.TelemetrySaveService] - Unable to open Telemetry VARA object 'UC_TELEMETRY_SETTINGS' for writing.
2026-02-10 13:18:08,825 pool-2-thread-1634     [ERROR] AWI_Connection_name:0100/AUTOMIC/AUTOMIC node0ejopd9m1kbxs8y6o1c177mv83-1 0000000001261010 +LOAD 7583 [com.uc4.ecc.plugins.telemetry.TelemetrySaveService] - Save of UC_TELEMETRY_SETTINGS failed
java.lang.NullPointerException: Cannot invoke "com.uc4.api.objects.Variable.remove(String)" because "com.uc4.ecc.plugins.telemetry.TelemetryVara.vara" is null
...

 

 

Environment

AE and AWI: 24.4.1 (any any hotfix of 24.4.1)

Cause

The ultimate cause of this is when logging into the system, users will update UC_TELEMETRY_SETTINGS - this is as designed; however, the object in some cases is locked.  When this happens while using 24.4.1, this popup shows up.

Resolution

Resolution: To suppress the popup window, the AE and AWI should be updated to 24.4.2 or above.

The underlying error in the AWI logs is planned to be fixed with 24.4.4 (currently planned for a March, 2026 release) with DE181725.

Possible workaround:

When the error appears, you might be able to log in to client 0 and open UC_TELEMETRY_SETTINGS.  Then click the "Edit" button on the upper left side of the object and close the object.  This should release the lock on the object.  

The reason the issue happens is because something is locking the object and by opening the object and being sure your user is editing the object and then closing it, you're releasing the lock.