ITADM112E Database Error (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"vault_system" WHERE 1=1 FOR UPDATE

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

ITADM112E Database Error (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"vault_system" WHERE 1=1 FOR UPDATE

L7 Applicator

I saw this error in my LAB environment when I tried to stop and start server service but once restarted , error is not occurring and cannot reproduce .

Anyone experienced this error and what might have caused this ?

1 accepted solution

Accepted Solutions

L7 Applicator

I saw this a couple of times in my lab environment, but also couldn't reproduce it. My thought is that it only happens if the vault has a high uptime (my guess: 1+ years ) or transaction volume. CyberArk should definitely investigate it, but since it doesnt seems to have any adverse effects, I haven't opened a case (yet).

View solution in original post

23 REPLIES 23

L7 Applicator

I saw this a couple of times in my lab environment, but also couldn't reproduce it. My thought is that it only happens if the vault has a high uptime (my guess: 1+ years ) or transaction volume. CyberArk should definitely investigate it, but since it doesnt seems to have any adverse effects, I haven't opened a case (yet).

L7 Applicator

I can relate the issue , Had not restarted the service in months. Thanks @Bernhard Brückler​ 

L4 Transporter

I set up a net new environment in non-prod and saw this error....bug?

L1 Bithead

I have also seen this error on many of our customer's italog.

L3 Networker

yes, 4.10. Just happened on startup. It had been at least several weeks since a restart, possibly longer. Can check if nec. Also had changed an IP address in the syslog XSL file we are using for PTA. But everything appears to be running, Vault is running. Queries OK, etc.

L4 Transporter

Restart the service and it will be ok

L2 Linker

Saw this in our PROD environment after restarting the PrivateArk server. Hoping it's noting serious.

Have see this error multiple times now and nothing serious

L4 Transporter

Seeing this same error. Any update or solution on the this?

L1 Bithead

Hi Guys,

Is there any solutions and root cause of the error? I am going to open case but hoping someone expert or know how to resolve the issue before the ticket opened should be helping.

 

Thanks.

L4 Transporter

Second time I've noticed that error. I usually stop the Vault once per month to install Windows Updates, and everytime I wonder what's happening but so far there hasn't been any consequences. If CyberArk wants me (or someone else) to open a case and provide debug logs, I'll assist as much as possible.

L4 Transporter

I also have seen it numerous times, and have been told it's benign. Would be nice to not be in the logs though!

It would indeed be nice. I'm comforted that they say it's benign, but I'd be more comforted if they said why it was happening.

L1 Bithead

I'm seeing this pop up frequently for a while and then stop on a few satellites. This was after rebooting them aswell.

  • 1 accepted solution
  • 5177 Views
  • 23 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!