During the High Availability (HA) database failover, all Automic Automation Work Processes (WPs) unexpectedly stop and shut down. Instead of transparently reconnecting to the new primary node, the engine encounters errors indicating the database is in a read-only state, leading to a complete system outage.
Symptoms:
All WPs terminate simultaneously during DB maintenance or failover events.
The following error messages appear repeatedly in the observer.log or WP logs:
U00003590 UCUDB - DB error: 'S0002', 'Failed to update database "Automicdatabase" because the database is read-only.', '3906', 'com.microsoft.sqlserver.jdbc.SQLServerException'U00045014 Exception 'com.automic.database.api.DBException: "UPDATE MQSRV SET MQSRV_LastUpdate = ..."
Product: Automic Automation Engine
Version: 24.4.4
Database: Database with High Availability / Always On Availability Groups
This behavior is identified as a software defect (DE183738).
A fix has been developed to improve the Engine's resilience during DB role transitions, ensuring it waits for the database to become writable rather than terminating the processes.
Fixed Versions: The fix is scheduled to be included in the following releases (dates tentative):
Automation Engine 24.4.4 HF1
Automation Engine 24.4.5
Automation Engine 26.0.0
Automation Engine 26.1.0
Public Title: WP server with MS SQL database continues to work if the database is read-only.
Public Description: A problem has been fixed where a WP server with an MS SQL database would still work even when the database was read-only.