We faced exactly the same issue and found Database Auto_Close Option is set to 'True'. We set it False and put database offline and online. The error message stopped popping up soon after this. Still don't know why this option when set ON lead started triggering this error message because log was not corrupted and we were able to query on the database. :exclamation: :ermm: