- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-16-2026 05:02 AM
Parameter DebugLevel has been dynamically updated.
ITADM112E Database Error (ITADM112E Database Error (Lost connection to MySQL server during query). ).
ITADM112E Database Error (Lost connection to MySQL server during query).
ITATS780E Failed to set transaction to read-only mode (error: ITADM112E Database Error (Can't connect to MySQL server on 'localhost:3306' (10061)). ).
ITAUI418I UI input is down. No more requests are accepted.
ITADB365I Waiting on 1 active task(s)...
ITADM112E Database Error (Lost connection to MySQL server during query).
ITADM112E Database Error (Can't connect to MySQL server on 'localhost:3306' (10061)).
ITATS781E Failed to set transaction to read-write mode (error: ITADM112E Database Error (Can't connect to MySQL server on 'localhost:3306' (10061)). ).
ITAUI420I UI output is down.
ITADB315I Server has normally terminated
ITAFW002I Firewall is closed to client communication
ITADM112E Database Error (Can't connect to MySQL server on 'localhost:3306' (10061))
04-16-2026 07:10 AM
I am working with the similar problem for customer - the only difference is there it occurred on DR Vault and "ITADM112E Database Error Can't connect to MySQL..." is visible in PADR.log while starting replication process, not the ITAlog like yours.
Anyway, I have raised a support case and their answer is to rebuild database. If this is fresh deployment I would recommend just to deploy a new vault for you but if this was working deployment you should rebuild the database and replicate data from another vault.
Actually it leads me to following conclusion as I have never seen such error messages before - recent occurrances of this problem means there is maybe a global problem with some update/patch version of CA Vault?
04-16-2026 05:33 AM
Hi,
Looks like there is an issue connecting to MySQL server. Try this article - https://community.cyberark.com/s/article/Vault-ITADM112E-Database-Error-Can-t-connect-to-MySQL-server-on-localhost-10061-when-shutting-down-the-Vault-server
Hope it helps
04-16-2026 06:19 AM
@Madat Yuzbashli ,
Thanks for revert
KB Article seems to be a preventive measure to avoid the DB Error Any Resolution or any changes to be done on Vault configuration to overcome this Error
04-16-2026 07:10 AM
I am working with the similar problem for customer - the only difference is there it occurred on DR Vault and "ITADM112E Database Error Can't connect to MySQL..." is visible in PADR.log while starting replication process, not the ITAlog like yours.
Anyway, I have raised a support case and their answer is to rebuild database. If this is fresh deployment I would recommend just to deploy a new vault for you but if this was working deployment you should rebuild the database and replicate data from another vault.
Actually it leads me to following conclusion as I have never seen such error messages before - recent occurrances of this problem means there is maybe a global problem with some update/patch version of CA Vault?
04-16-2026 07:20 AM
Hi @Korneliusz Lis,
Thanks for Solution Suggested!
Adding more info it's a fresh deployment of V 14.2 CA Vault
09-02-2026 07:46 AM
Hello @GANESH K
Were you ever able to come to a resolution of the error? I saw this error on a newly built stand alone 14.2 server myself. I rebooted the server and it appears to be working fine right now but would like to know if there are more difficult processes in my future.
thank you!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

