"Other concurrent activities have reused the available space in the database that contained your snapshot of data. This can occur with time consuming tasks such as printing or making backups. Wait until there are fewer concurrent updates of the database and try again. We have isolated the exact record causing the problem. Unfortunately we cannot delete, view, export the record without getting the error message. Any ideas how we can delete the bad record?
quote:
Originally posted by mblauer
"Other concurrent activities have reused the available space in the database that contained your snapshot of data. This can occur with time consuming tasks such as printing or making backups. Wait until there are fewer concurrent updates of the database and try again. We have isolated the exact record causing the problem. Unfortunately we cannot delete, view, export the record without getting the error message. Any ideas how we can delete the bad record?
Did you try to run a dataport exporting all records but the corrupted one? That is - first have the dataport processing records from the first one to last before the corrupted record; then have the same dataport processing all the remaining records starting from the first after the abovesaid record. If you can do that, you can also empty the table and re-import the previously exported records. A similar solution for a similar problem was suggest by somebody else, some time ago, but I couldn’t locate it in the archive. So I tried to summarize it for you. [:D] Anna
Yes I exported all the good records. How does that get rid of the bad record?
Then you make a batch job that deletes all records in the table, or delete them all from the Object Designer, Tables, Run, and then delete them all. After that, you import the records you exported with the dataport, and you manually recreate the bad record. BUT FIRST!!! You make a bckup!!
When I use a report to delete the bad record I get the error message.
Totally out of the subject but Lars I love your signature. Took me a little to get it 
Cristi Nicola
Then you make a codeunit with one statement in it. Table.DELETEALL(FALSE);
What version of C/SIDE are You using?
Version 2.6.
Then You should upgrade to 3.10 where these kind of errors has been fixed. We hade a client with a lot of problems like this, and since upgrading C/SIDE to 3.10, the problems has stopped. //Lars
Just in case you’re not aware, you can almost always upgrade the C/SIDE executables to a more recent version without upgrading your application objects. That is, of course, assuming your license supports the upgrade. Moving to V3.10 executables from V2.6 does require a license upgrade from Navision. And just in case there is something unique about your situation, a test with a copy of the production database first is always appropriate.
We are recovering by writing the codeunit table.deleteall. The bad data was deleted in hte table. Navision Atlanta and our NSC never usggested doing this. Navision Atlanta was useless, their response was go back to your last backup or send us the database and we might be able to repair it. We will definitely upgrade ASAP. I only wish we had this info two days ago. Thanks Lars!