A customer has been running a C/S app based on EDB 2.03b9 (ANSI) since 2010 on a Windows Server 2003 machine.  Now they want to move to a Windows Server 2016 machine.

After moving all the files I thought were needed, I tried to start edbsrvr 2.03b9, and received the error "ElevateDB Error #400 The collation ZZZ already exists in the configuration EDBConfig."

I placed EDB 2.27b1 on the machine.  It starts without error, and EDB Manager can open the old database without a problem.

At home I recompiled the 2010 program using Delphi 2007 and EDB 2.27b1 on a Win7 32-bit virtual machine--there were no issues except the warning about some missing temp table properties (I guess the items mentioned in the 2.25 release note).  The recompiled program works perfectly at home...but when moved to the Windows Server 2016 machine, the program reports error #400 again:

"Exception EEDBError in module Flocks.exe at 001E1E7F. ElevateDB Error #400 The collation ZZZ already exists in the configuration EDBConfig."

I have no idea what to do next, so will be thankful for any advice...

Charles


That's weird. As far as I know we can't add collations only Tim (or possibly Windows) can do that. Looking in the manual the 400 error seems like a slight misdirection and I'd guess the below is more appropriate:

<<
You may query the system-created
Configuration database to get a list of available collations. All available collations in the operating system are stored in the Collations table in the Configuration database. For example, the following SELECT statement returns all of the available collations:

SELECT * FROM Configuration.Collations

You will receive an error if you try to open a database that has table columns or index columns that reference a collation that is not available on the operation system being used.
>>

<<
The collations in ElevateDB are dynamic and this table reflects the available installed collations (locales) in the operating system. See the
Internationalization topic for more information on collations.

>>

So as a further guess you had a custom collation on the old server which is no longer present  but is being requested. Try

select * from information.tablecolumns where Collation = 'ZZZ'

to see if anything like that is defined. If nothing found than search your source (pas & dfm) for ZZZ.

In case ZZZ is also misdirection try

select distinct collation from information.tablecolumns

might give you a start



Roy Lambert

Charles,

<< A customer has been running a C/S app based on EDB 2.03b9 (ANSI) since 2010 on a Windows Server 2003 machine.  Now they want to move to a Windows Server 2016 machine.

After moving all the files I thought were needed, I tried to start edbsrvr 2.03b9, and received the error "ElevateDB Error #400 The collation ZZZ already exists in the configuration EDBConfig."

I placed EDB 2.27b1 on the machine.  It starts without error, and EDB Manager can open the old database without a problem. >>

Did you try to start the 2.27 *EDB Server*, or just the EDB Manager ?

Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

Charles,

<< A customer has been running a C/S app based on EDB 2.03b9 (ANSI) since 2010 on a Windows Server 2003 machine.  Now they want to move to a Windows Server 2016 machine.

After moving all the files I thought were needed, I tried to start edbsrvr 2.03b9, and received the error "ElevateDB Error #400 The collation ZZZ already exists in the configuration EDBConfig."

I placed EDB 2.27b1 on the machine.  It starts without error, and EDB Manager can open the old database without a problem. >>

Did you try to start the 2.27 *EDB Server*, or just the EDB Manager ?

I started edbsrvr without error (as an application, not a service), then connected EDB Manager via a remote session.



Tim Young
Elevate Software
www.elevatesoft.com

Charles,

<< I started edbsrvr without error (as an application, not a service), then connected EDB Manager via a remote session. >>

Okay, I'm still a little confused.  Are you using the 2.27 EDB Server in all instances ?

In one sentence you state that the 2.27 EDB Server worked fine on the Windows 2016 Server ("I placed EDB 2.27b1 on the machine.  It starts without error, and EDB Manager can open the old database without a problem."), while in the other you state that the 2.27 EDB Server encountered an error ("The recompiled program works perfectly at home...but when moved to the Windows Server 2016 machine, the program reports error #400 again").

Both of those statements cannot be true.

Tim Young
Elevate Software
www.elevatesoft.com