View Incident Report

Serious

Reported By: Dale Derix
Reported On: 2/10/2011
For: Version 2.05 Build 3

# 3386 EDB Incorrectly Allowing Configuration Objects to be Renamed to an Existing Object

I renamed user Kim to Dale where Dale already exists using the following SQL. No errors.

he server is still running, but if I then start ElevateDB Manager, it reports the same error when it tries to connect to it.

If I shut down the server and restart it, I get the following error and the server will not start:

"ElevateDB Error #400 The user Dale already exists in the configuration Config"

RENAME USER "Kim" to "Dale"

Comments

In general, EDB was not checking for duplicate object names when configuration objects were renamed.

Resolution

Fixed Problem on 2/14/2011 in version 2.05 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