DB Restore problem


I do have a problem with the restoring db. I’m restoring NAV 5 db Classic into NAV 2009 R2 db Classic (Demo). All is going well with the restoring however for some reason after the restore all objects (forms, codeunits, etc.) except tables are empty as there is nothing in the object designer for them. It could be still Ok as I could export and import missing objects (Forms, codeunits, etc.). But, the tables object IDs seem as corrupted as they have some additional numbers in front of the standard object id codes.

E.g. GL that should be 17 has 1000000017; GL Register – 1000000045 instead of 45, etc.

On the SQL Server tables names look as follows that is not right as well:

dbo.CompanyName$G_L Entry1000000017

dbo.CompanyName$G_L Register1000000045

I didn’t apply a company license before restoring so probably I should have done it before doing it or different versions could cause the corrupted tabled IDs I’m not sure.

Please, help.


It means that your restore process was not finished.

Click tools–>Restore again…

it will start the process automatically…

Thank you for the advice, Mohana. So, I tried the restore again and it’s starting but I’m getting the error : “You cannot delete or change the type of the Description field (in the Database Key Groups table) before the value in the field reduced to 0 (zero) or ‘’ (blank) in all records. This message occurred because a nonzero value was found for the record Key Group=ACC(CONS)’ in company.”

Could you please, advise how I could handle with it.


If you can Alexander, I’d think your best bet at this point would be to abandon the current restore operation as well as the target database, and start fresh with a new database. It’s a far more economical approach than chasing this error.

You didn’t mention it in your original post, but I’m assuming that you’re trying to restore into a new, previously unused database? I ask because, if you’re restoring a database into an existing database that potentially has different objects that what you have in the backup, you could run into this kind of error. Granted, it probably wouldn’t be related to the table you’re getting errors on, but you could expect the same type of error.

So, I’m thinking do-over …

Thank you, George. It did work with a fresh db.