I am getting very frequent errors in the PI System.
Failed to lock buffer source for reading, [-16212] Timeout attempting to get non-exclusive lock.. Point ID ###### (regid=0/42)
This issue usually happens if the Data Archive is resource limited. That is to say, if it doesn't have enough RAM or Processing power to adequately handle of the requests being sent to it (whether that be reads fr data, or writes of new events.) Could you open up task manager and see if there is a low amount of free memory or a consistently high CPU usage?
There were also some known issues with 2015 R2 release of the data Archive described in KB01332 which could cause these issues. What version of the Data Archive are you running?
Thanks for the details, we are using 2016 R2 Version.
The CPU Usage is normal around 30-40 % of Utilization.
If the CPU utilization looks normal and you're not hitting any known issues then I would recommend calling into Tech Support as the next step from here is to take a look at the thread statistics for the archive subsystem, which I would recommend having an engineer on the line for to assist in interpreting the results. I suspect that there is probably a long running/expensive query that are locking the point(s) from being written to.
Does this error happen with a number of pointID's or just a specific subset? If it's a specific subset there's good odds one particular application/query is locking them for too long. If it's every pointID then it's still possible there's a resource limitation somewhere like disk I/O preventing the system from adequately handling the requests; for example a backup occurring while points are being written to the system. Although that's generally not the case because backups tend to be run in off business hours and wouldn't run around the clock causing the issue to happen at all times of the day.
Retrieving data ...