View Incident Report

Serious

Reported By: Arnd Baranowski
Reported On: 1/27/2015
For: Version 2.18 Build 3

# 4149 Invalid Default EDB Signature Used when Configuring the ElevateDB Server to use ANSI Character Set

I had been working for a long time with EDB Version 2.11 Build 3 client server with source because I am very reluctant on updates. During this time I did decide to go for the engine signature "<signature>". Now I did upgrade to the latest version 2.18 Build 3 and it does not let me run with this signature anymore. I may open server and manager with signature "edb_signature" only. However then I may not access all the databases which had been generated since I did decide to go for signature "<signature>" and there is no way to use "<signature>".

Comments

The problem was introduced during the ANSI/Unicode changes to the engine that allowed the engine to use both types of databases. The default signature digest was not being updated properly internally when the character set of the engine was changed dynamically. This would happen when the server/application was compiled with a Unicode version of the compiler (the shipped EDB Server/EDB Manager are compiled with a Unicode compiler), but the character set was set to ANSI.

Resolution

Fixed Problem on 1/28/2015 in version 2.18 build 4

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

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap