# 3090 Dead Sessions on the EDB Server Containing Updateable Views Can Cause Lock Errors

---

App1 and App2 are accessing the same database "Informa". App1 accesses a field that is not existent in the database and is thus terminated leaving a dead session. (Normally that doesn't happen off course, I just ran it to produce a dead session.)

This produces the lock error for sure on my computer:

1. Starting EDBSrvr.exe
2. Starting app1 - error message (field xy not found).
3. app1 is closed leaving a dead session
3. Opening app2: no error, dead session still present
4. When the dead session is removed after timeout:
5. Opening app2 results in #300 error.
6. This error continues until EDVSrvr is restarted.