Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Enhancement Requests and Suggestions » View Thread |
Messages 1 to 5 of 5 total |
Error 100 |
Mon, Mar 9 2020 5:57 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | I just received an error 100 on a table. The table in question was last used on Saturday and was fine then. Although its part of an app in development no changes to the table structures have been made for weeks. I restored Friday's backup and am back in business.
The request is can we have a bit more information as to what has caused the error. The current error message tells me its toast and that's it --------------------------- ElevateDB Manager --------------------------- ElevateDB Error #100 There is an error in the metadata for the table Banks (The internal structure does not match the structure in the catalog) --------------------------- OK --------------------------- Roy Lambert |
Wed, Jul 1 2020 6:14 AM | Permanent Link |
codealfa | Hi,
sadly sometimes we too get this message. When our app doing a table reindex or restructure and in the background and another instance of this app doing an index checking, the internal signatures are mixing and the data of the table are usually lost. Only the restore data helps. It would be very good it this problem can be gone. |
Thu, Jul 2 2020 2:06 AM | Permanent Link |
Yusuf Zorlu MicrotronX - Speditionssoftware vom Profi | codealfa wrote:
> Hi, > > sadly sometimes we too get this message. > When our app doing a table reindex or restructure and in the > background and another instance of this app doing an index checking, > the internal signatures are mixing and the data of the table are > usually lost. Only the restore data helps. > > It would be very good it this problem can be gone. If this really happens in such cases, this is a very important bug and should be fixed asap by ElevateDB. -- -- Yusuf Zorlu | MicrotronX |
Sat, Jul 4 2020 3:05 AM | Permanent Link |
codealfa | There is a important missing information from previously message,
the problem usually exists, when a table repair runs (on good tables), (because there was a incorrect program exit) then there is a power outage or reboot on computer, then the two instance of app try to verify and repair the tables. The strange thing: not only one table is corrupted but 5-10. |
Mon, Jul 6 2020 3:13 AM | Permanent Link |
Yusuf Zorlu MicrotronX - Speditionssoftware vom Profi | codealfa wrote:
> There is a important missing information from previously message, > the problem usually exists, when a table repair runs (on good > tables), (because there was a incorrect program exit) > then there is a power outage or reboot on computer, > then the two instance of app try to verify and repair the tables. > > The strange thing: not only one table is corrupted but 5-10. Good to know. Thanks for this update. -- -- Yusuf Zorlu | MicrotronX |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |