---

 Comments and Workarounds

---

This issue was caused by the fact that ElevateDB Server threads cache the server encryption settings for performance purposes, combined with the fact that the ElevateDB Server itself caches the threads (based upon the server's thread cache size setting).

The workaround was to restart the ElevateDB Server process when changing the server encryption password after sessions have already connected to the ElevateDB Server using the older encryption password.

The ElevateDB Server also now issues an error if you attempt to modify the server settings and do not include a server encryption password.

---

 Resolution

---

Fixed Problem on 4/12/2018 in version 2.28 build 1

---

 Products Affected

---

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