# 3896 Using an In-Memory Configuration Can Cause a Database Locking Error

---

I think I have found a locking bug in ElevateDB, although I haven’t been able to find the cause I can reliably reproduce it under very specific circumstances:

- Using in-memory database configuration
- Setting Session property KeepConnections to false
- Accessing the same Database from multiple Processes (this may be a red herring, but only way I have reproduced so far)
- In the process where the error occurs access the same Database in two or more Sessions

An ElevateDB Error #300 occurs when a Session attempts to reopen a Database for a second time (its previous copy having been thrown away due to the KeepConnections property).