Access violations are a rare occurrence, but are always possible due to a bug in the ElevateDB Server. In such cases, one must use a debug version of the ElevateDB Server in order to help us track down the location and cause of the bug. This is especially true with bugs that only manifest themselves at runtime in a production environment.

All Client-Server versions of the ElevateDB products include debug versions (32-bit and 64-bit) of the ElevateDB Server that can be used to create dump files (*.edbdmp) when when such unhandled exceptions occur.


The ElevateDB Server dump files are just text files that contain memory and call stack snapshots that capture a picture of the runtime environment when the unhandled exception occurred, and will be found here:

C:\Users\<UserName>\AppData\Local\Temp

where <UserName> is the user account under which the ElevateDB Server is running when the dump file was created.


Each dump file will look like this:

error<Date>-<Time>.edbdmp

<Date> - yyyy_mm_dd
<Time> - hh_mm_ss_zzz

When the ElevateDB Server creates one or more dump files due to unhandled exceptions, make copies of the dump files and email them to support@elevatesoft.com.

You can find the debug versions of the ElevateDB Server in the following location in the ElevateDB product installation directory:

<InstallDir>\servers\edbsrvr\debug\win64\edbsrvr.exe
<InstallDir>\servers\edbsrvr\debug\win32\edbsrvr.exe

These debug versions of the ElevateDB Server use a different .ini file directory:

C:\ProgramData\Elevate Software\ElevateDB Server (Debug)\edbsrvr.ini
C:\ProgramData\Elevate Software\ElevateDB Server (Debug-Win64)\edbsrvr.ini

so be sure to copy any existing edbsrvr.ini file from the appropriate default location:

C:\ProgramData\Elevate Software\ElevateDB Server\edbsrvr.ini
C:\ProgramData\Elevate Software\ElevateDB Server (Win64)\edbsrvr.ini

to the debug server's .ini directory so that the debug server uses the proper settings for the installation.