I get this error frequently as well. It started about a year ago and persists through all the updates and releases. The only way I've found to fix it is to log out and restart the host computer. I only have two users and one background process that accesses the database.  I hope you find a solution, I have not.