- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-22-2019 07:53 AM
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 ?
01-22-2019 07:57 AM
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).
01-22-2019 07:57 AM
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).
01-22-2019 08:01 AM
I can relate the issue , Had not restarted the service in months. Thanks @Bernhard Brückler
02-19-2019 08:23 AM
I set up a net new environment in non-prod and saw this error....bug?
02-19-2019 11:25 PM
I have also seen this error on many of our customer's italog.
04-29-2019 04:48 PM
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.
05-09-2019 06:03 PM
Restart the service and it will be ok
05-15-2019 09:09 AM
Saw this in our PROD environment after restarting the PrivateArk server. Hoping it's noting serious.
05-15-2019 11:13 AM
Have see this error multiple times now and nothing serious
05-15-2019 01:18 PM
Seeing this same error. Any update or solution on the this?
08-15-2019 04:04 AM
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.
09-19-2019 05:39 PM
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.
09-20-2019 01:22 AM
I also have seen it numerous times, and have been told it's benign. Would be nice to not be in the logs though!
11-04-2019 08:53 AM
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.
06-18-2020 10:15 AM
I'm seeing this pop up frequently for a while and then stop on a few satellites. This was after rebooting them aswell.
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!

