I have a database created in 2.03 and was trying to upgrade the customer to the current version 2.16 but ran into problems where the new program couldn't seem to connect to the database any longer.  Both versions of the program are created in Delphi 6 running under Windows XP.  To check into it I used edbManager to verify that I could work with the database.

I can connect to the database using the edbManager 2.03 (SessionType Local) and see all of the tables.  But when I connect to the database using edbManager 2.16 (Build 2) I get the follow error
"ElevateDB Error # 100 There is an error in the metadata for the configuration VPTConfig (The signature does not match the default or current engine signature)"

VPTConfig is just a renamed EDBConfig.  I went back into edbManager, did an Edit Session, and switched the character set to ANSI as the new version defaults to Unicode.  No luck.  I still get the same error.  

If I use edbManager 2.03 again it works just fine so the basic configuration information is correct otherwise I wouldn't be able to connect with the old manager

I found the fix utility and ran it with the 'overwrite' option but that didn't make any difference.  The noticeable difference between the configuration files is that the 2.16 version has an encryption value that must be filled in.  The old one doesn't but I would expect an encryption error not a signature error.

My understanding is that the database files themselves didn't change between versions but that the catalog table did

I'm guessing that once I get edbManager 2.16 connecting to my database that my new program will work as well.

Where do I look next?

Thanks
Richard

Todd Neuman wrote:

> Where do I look next?

If no one has an answer, raise a support ticket with Tim, and he'll
know.

--

Matthew Jones

Todd


I'm not sure what sequence things happen in during start up but I seem to recall that the encryption being wrong can result in an error revering to the signature (the way my memory is these days I could be wrong).

You don't say wether your program will work using 2.16 (why not go for the latest 2.19?) but if it will why not simply cheat. Reverse engineer the database in 2.03 and run the resulting sql in 2.16


Roy Lambert

ps - D6 & XP wow - I thought I was primitive with D2006 & W7

Todd


The other thing you can do in EDBManager is to look at the ini files that hold the session definitions and see if there are any differences. Its a lot easier to compare with plain text files.

Roy Lambert

Hi Roy

The current program doesn't work against the old database.  I was using Manager to try to figure out why.  

I was wondering about the encryption as 2.03 didn't have encryption at all but 2.16 forces you to have it filled in with something.  

Our new development is under Delphi XE7 in W7 but the current version is still hanging in there under D6.  You can't have too many development environments going. Thank the stars for virtual machines!

I hadn't thought of the reverse engineer option.  I may do that as plan B but it would be nice to understand where I am being blocked (in case it happens again)

Thanks for your thoughts

Roy Lambert wrote:

Todd


I'm not sure what sequence things happen in during start up but I seem to recall that the encryption being wrong can result in an error revering to the signature (the way my memory is these days I could be wrong).

You don't say wether your program will work using 2.16 (why not go for the latest 2.19?) but if it will why not simply cheat. Reverse engineer the database in 2.03 and run the resulting sql in 2.16


Roy Lambert

ps - D6 & XP wow - I thought I was primitive with D2006 & W7

I thought both EDBManager versions use the same ini file and that's why I was sure the settings were the same for both versions

Roy Lambert wrote:

Todd


The other thing you can do in EDBManager is to look at the ini files that hold the session definitions and see if there are any differences. Its a lot easier to compare with plain text files.

Roy Lambert

I realized that I wasn't being clear when I talked about connecting to the database.  I am actually getting that error when I try to connect to the session itself.  I'm not getting as far as connecting to the database. I am thinking that I am going to have to go the router of creating everything from scratch and just repopulating the new version of the database with the old data

Thanks


Todd Neuman wrote:

I have a database created in 2.03 and was trying to upgrade the customer to the current version 2.16 but ran into problems where the new program couldn't seem to connect to the database any longer.  Both versions of the program are created in Delphi 6 running under Windows XP.  To check into it I used edbManager to verify that I could work with the database.

I can connect to the database using the edbManager 2.03 (SessionType Local) and see all of the tables.  But when I connect to the database using edbManager 2.16 (Build 2) I get the follow error
"ElevateDB Error # 100 There is an error in the metadata for the configuration VPTConfig (The signature does not match the default or current engine signature)"

VPTConfig is just a renamed EDBConfig.  I went back into edbManager, did an Edit Session, and switched the character set to ANSI as the new version defaults to Unicode.  No luck.  I still get the same error.  

If I use edbManager 2.03 again it works just fine so the basic configuration information is correct otherwise I wouldn't be able to connect with the old manager

I found the fix utility and ran it with the 'overwrite' option but that didn't make any difference.  The noticeable difference between the configuration files is that the 2.16 version has an encryption value that must be filled in.  The old one doesn't but I would expect an encryption error not a signature error.

My understanding is that the database files themselves didn't change between versions but that the catalog table did

I'm guessing that once I get edbManager 2.16 connecting to my database that my new program will work as well.

Where do I look next?

Todd

>I thought both EDBManager versions use the same ini file and that's why I was sure the settings were the same for both versions

It does when you install it, I thought you had installed in separate machines or VMs.

I did have some problems when Tim switched over to a common code base for unicode & ansi but I don't remember anything like this.

Roy Lambert

Todd

>I realized that I wasn't being clear when I talked about connecting to the database. I am actually getting that error when I try to connect to the session itself. I'm not getting as far as connecting to the database. I am thinking that I am going to have to go the router of creating everything from scratch and just repopulating the new version of the database with the old data

Before you do that just create a new session and point at the existing database. It "should" work.

Roy

I did try creating a new session and pointing it to the database.  I got the same error.  It is strange as I have a number of clients who I have moved to the new version without this problem

- Create new Session
- Change Character Set to ANSI
- Point to the same folder as the old configuration files
- Change the Configuration Name from EDBConfig to our standard name
- Change the signature to our standard signature
- Fill in the login username and password
- Press [OK]
- Attempt to connect
- Error #100 (The signature does not match the default or current engine signature)

If I exit edbManager 2.16 and start up edbManager 2.03 and point it to the same new session it works

I also sent Tim an email but haven't heard anything back yet

> Before you do that just create a new session and point at the existing database. It "should" work.

Roy