---

 Comments

---

This was caused by some locking changes in 2.22 to improve concurrency under heavy contention. The changes inadvertently affected the way that the remote session lock timeouts were set, thus causing lock errors to appear when they shouldn't have been. This type of lock contention could occur when using server requests in timers and the request conflicted with the pinging thread for the remote session pinging the EDB Server.

---

 Resolution

---

Fixed Problem on 3/20/2016 in version 2.23 build 1

---

 Products Affected

---

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial