My company has been using Navision 2.0 since 1999 and recently got a “There is a corrupted area in the database.” error. It offered a lengthy set of procedures that included test, copy database (using a basic right-click & copy), backup database (using the backup tool). The same msg appears when doing the Test and/or backup, preventing both procedures from working. Step 3 of the message says “If this works…” then basically you’re golden. then it goes on to say “If this procedure doesn’t work…” I have to restore an older backup from a time when the db was not corrupt. My problem is I was on vacation for 2 1/2 weeks and the error occurred the day I left! Nobody here addressed the issue, so now my most recent backup is 3 weeks old, which means 10 people re-entering 3 weeks worth of data!!! (provided the old backup is ok, which I am testing on an isolated server right now). Does anyone have an alternative solution? Database repair tools or methods, etc… Can I fish out the corrupted data?? Navision seems to be working just fine otherwise, except for posting Bill of Material only on certain items. Thanks in advance, Bryan
Try to get in touch with Navision USA. They might be able to rescue the data.
In my experience this error message can either mean one of two things: Either the database IS actually corrupt (main cause would probably be a faulty harddrive) or you have external processes that have inserted invalid data. I had this error message for one of my clients just three weeks ago. It turned out to be their web inserting invalid data (it inserted lower-case characters in a code field). I think the error message actually gives you the table where the corrupt data is. If you know this, then you can do some different things in order to clean this up. You might end up having to delete the whole table, but in my case I just had to make everything upper-case. If you really have a corrupt database, I think Navision will be able to help you recover the information (but if I remember correctly, it isn’t especially cheap). Good luck (and remember to always, always do a daily backup…) Daniel
Hi Bryan. As Daniel points out you can try to re-enter the data for the few tables you know are corrupt. In your case I would re-enter the BOM tables for those “certain items” you mentioned. THIS MIGHT SOLVE THE PROBLEM! IF you still have a problem you could as Step 2 export the BOM tables using a dataport, delete the data and import it back in. If you can not do Step 2 (as the data is to much corrupted) you will try to get this data from the backup if you manage to restore it. You might try to do this for all the “static” tables. Hope this helps.