Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 6 of 6 total |
Error #100 woes |
Mon, Oct 10 2011 2:01 AM | Permanent Link |
TonyWood | I started to get the following error (possibly caused by running a different version of edbsrvr ?)
ElevateDB Error #100 There is an error in the metadata for the configuration EDBConfig (The object has been updated by a newer version of the engine). So I pointed the session to a different EDBConfig and recreated the database. Now when i try to access that database I'm getting : ElevateDB Error #100 There is an error in the metadata for the catalog <DB_Name> in the database <DB_Name> (The object has been updated by a newer version of the engine). What do i have to do now ? What could I have broken ? Thanks in advance Tony Wood |
Mon, Oct 10 2011 10:50 PM | Permanent Link |
TonyWood | I fixed the problem by deinstalling the 3 EDB packages and upgrading to the latest 2.05b11
|
Tue, Oct 11 2011 12:44 AM | Permanent Link |
TonyWood | No, I was wrong, I still have the Error #100 problem.
On a 16 core server, I try to start 16 instances of the edbsrvr from a shell script, the first 8 start OK, the rest silently refuse to start, then get Error #100 when i try to start them from their icon in the system tray filename port result edbsrvr1 12011 Runs ok as background process edbsrvr1 12012 Runs ok as background process edbsrvr1 12013 Runs ok as background process edbsrvr1 12014 Runs ok as background process edbsrvr1 12015 Runs ok as background process edbsrvr1 12016 Runs ok as background process edbsrvr1 12017 Runs ok as background process edbsrvr1 12018 Runs ok as background process edbsrvr1 12019 Will not start gets Error #100 edbsrvr1 12020 Will not start gets Error #100 edbsrvr1 12021 Will not start gets Error #100 edbsrvr1 12022 Will not start gets Error #100 edbsrvr1 12023 Will not start gets Error #100 edbsrvr1 12024 Will not start gets Error #100 edbsrvr1 12025 Will not start gets Error #100 edbsrvr1 12026 Will not start gets Error #100 The actual error is : ElevateDB Error #100 There is an error in the metadata for the configuration EDBConfig (The object has been updated by a newer version of the engine) I'm trying to get load data into a database faster, by trying to take advantage of multiple edbsrvrs, as i have been unable to run a single edbsrvr instance on more than one cpu core. Am i going about it the right way ? Thanks Tony Wood |
Tue, Oct 11 2011 12:48 AM | Permanent Link |
TonyWood | sorry , cut and paste bug, FWIW each server instance has a different filename
filename port result edbsrvr1 12011 Runs ok as background process edbsrvr2 12012 Runs ok as background process edbsrvr3 12013 Runs ok as background process edbsrvr4 12014 Runs ok as background process edbsrvr5 12015 Runs ok as background process edbsrvr6 12016 Runs ok as background process edbsrvr7 12017 Runs ok as background process edbsrvr8 12018 Runs ok as background process edbsrvr9 12019 Will not start gets Error #100 edbsrvr10 12020 Will not start gets Error #100 edbsrvr11 12021 Will not start gets Error #100 edbsrvr12 12022 Will not start gets Error #100 edbsrvr13 12023 Will not start gets Error #100 edbsrvr14 12024 Will not start gets Error #100 edbsrvr15 12025 Will not start gets Error #100 edbsrvr16 12026 Will not start gets Error #100 |
Tue, Oct 11 2011 1:37 AM | Permanent Link |
TonyWood | OK, phew, it's fixed again now, i didn't overwrite all the edsrvrXX.exe instances with the new version
Sorry, my bad |
Tue, Oct 11 2011 3:34 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Tony,
<< I started to get the following error (possibly caused by running a different version of edbsrvr ?) ElevateDB Error #100 There is an error in the metadata for the configuration EDBConfig (The object has been updated by a newer version of the engine). >> This error is caused by using a newer version of ElevateDB to modify a configuration/databases, and then going back to an older version of ElevateDB and trying to use it with the updated configuration/databases. The solution is to make sure that you're using the same minor release of ElevateDB in all of the applications/servers that are accessing the same configuration/databases. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |