errors in the text conversion exist in the .stx file

khalilchahin

Hello All,

Before completing a full back up for my native navision 5.0 or before completing a back up for the application objects only I get this error:

There are errors in the text conversion(text no 1969-0 does not exist in the .stx file). Internal error:47-1

I get the same error when I try to run any of these tables in the object designer:
2000000069 Client Add-in
2000000071
2000000072
2000000073
2000000074
2000000075
2000000076
........
2000000080 Page Data Personalization.

I think what happend is that I tried to install Microsoft Dynamics Nav 2009 on a stand alone PC and for some reason when I opened this application it connected to the server and converted the native navision 5.0 DBase and created these tables.

would you please advise if I can delete these tables since I tried using the developer license but I couldn't ?

Thanks all for your help in this matter.

matttrax

Your database was in fact converted to 2009. I think there is a post here on Mibuso somewhere about how to convert it back to 5.0.

khalilchahin

matttrax wrote:

Your database was in fact converted to 2009. I think there is a post here on Mibuso somewhere about how to convert it back to 5.0.

Thanks for the reply but I am just wondering if there is anyway to delete these tables mentioned in my question. I think this will be easier than converting the Database back to 5.0 . These tables are the only indication of the conversion if it really happened.

Thanks again.

dblaisdell

My client has the same issue. somehow the tables 2000000065-2000000068 were created and now the backup fails due to Text no. 1965-0 does not exist in the .stx file. Developers license will not allow me to delete them. Did you find out how to delete the tables?

kcooper

How were you able to resolve this? We are going to test deleting the extra tables via SQL but this is not recommended from MBS. I did not find the doc on converting back to 5.0 that was mentioned. Any advice is welcome.

rdebath

I couldn't find the upgrade solutions list for V6 so ...

Downgrading from V6 to V5 is more of a problem than normal as Microsoft have infected Navision with the Microsoft upgrade treadmill™ approach.

If any object was recompiled under V6 you'll probably have to export it to text using V6 and delete the extra noise that's been added (ie empty RDLDATA, FIELDGROUPS, etc)

If you just did an "accidental upgrade" then did the backup and restore to V5 you'll have the extra tables you've noticed. (These table can also be imported to a V5 DB even though they're not valid there)

If you have data that's in the 'data for all companies' section I think you'll have to manually save that else where and reimport it at the end because these annoying tables will be there too. Eg if they're in the same SQL database you can used an INSERT ... SELECT statement to copy between DBs.

To get all the objects select all the objects in object designer (except the V6 ones) and export then as a FOB file. Rename the FOB file to Objects.FBK.

Restore the Objects.FBK file, USING Tools->Restore, into an empty database.
Backup and restore all the companies in the normal way.
Import your required 'data for all companies' from where ever you "saved" it. (eg: copy & paste ?)

You'll probably want to export then import the V5 objects for tables over 2000000000 from a Cronus V5 too so it looks nice and clean.

This message should also work fine if you global replace V5 by V4 or V3 too.

kcooper

R - Thank you. We'll try this. - k

pichon

i got similar problem, accidentally an user opened our NAV 5.01 database which is in native server option with the NAV 2009 Classic Client, so the database was unfortunately converted to the new version and after that we were not able to run a complete backup of the same database anymore in the nav 5.01 clients since there is a problem with certain tables already mentioned here and the only client where we can run backups with is the nav 2009, causing a problem for the end-user that runs the backup.

we run a backup every day so we were able to recover the last working backup but not from the day of the error. we were afraid to lose the data of the current day. so to fully recover the data i thought in a solution that help us to recover everything.

so this is my solution i hope it helps to someone else:

1. what we did was to create a full backup of the already converted db but with the NAV 2009 classic client. we will call it "current backup in NAV 2009 client".

2. with the NAV 5.01 client: create a new blank database and restore the backup of the day before of the error in the same database, the last backup that worked out. Tools -> Restore

3. after restored , open the companya as usual in the nav 5.01 but "delete" the company as the data is from the last backup but not from the current day.

4. still in NAV 5.01, after deleting the company, you will then have a database with all the correct obejcts but without data. So take the backup we created in the NAV 2009 client "current backup in NAV 2009 client" and restore it in this new database with correct objects and no data. in the restore dialog window you will only see the choice to restore data, that is correct , you already have the objects in the target db thus you only need the new company data.

5. once you restore the backup you will have a database with correct object set and current data.

i have not done the test but it should work in SQL as well creating a new SQL db with the same steps. the same if there are more than one company. of course be carefull with data common to all companies and make your own checks after completing this process to ensure you recovered everything.

hope this is useful, hasta la vista
Silvano Mendoza