Hotfixes have been released to fix various C/SIDE issues including ‘Internal Error 1355 in module 19’. (Maybe you know that one?) These are the versions and fixes: 3.10A Hotfix 14 - 1355 internal error 3.60 Hotfix 23 - 1355 internal error - Screen flicker esp. on Citrix - C/FRONT OCX memory leak - SQL: Performance with batch inserts - Application Server stopping during error 3.70 Hotfix 5 - All above 3.60 + … - SQL: Czech ‘CH’ character problem - SQL: Incorrect session list and counts - SQL: Index creation error after Altering Collation Note: The latter two include the performance degrade problem in SQL for batch inserts, which I posted a workaround for recently - this has been totally removed from these versions (and was not present in 3.10). Check for more info with your local MBS office.
I installed HotFix 5 for Navision 3.70 (SQL Option) today, and after that I can not open database: I have a error ‘TableData 20000000001 does not exist’. Thanks God I did it local on my test server! What to do??? I tried to switch back (old finsql.exe and ndbcs.dll), but database is converted (!!!) and I have a message that I have to upgrade to newer version (means HotFix 5). Do I really must deinstall all and then install HotFix 3&4 only ??
Do you know if the .stx file was different when you did the upgrade? It has to be the same .stx file as that used when creating the database, because Navision will update the [identifiers] field of the [$ndo$dbproperty] table with several table and fields names based on the contents of the .stx file in affect, when the upgrade is done. The table you mention is the Object table; if you do: select [identifiers] from [$ndo$dbproperty] from Query Analyzer what is the table name for 2000000001= ? I assume that this is not the name in the your SQL database. This is usually the cause of your problem.
Thanks for your support! I checked all *.stx files in Navision directory (fin, int and ImageSelector), and they are all dates from May or June 2003, so I think those files are not changed. Output from Query Analizer (Navision Demo Database) is 2000000001=“Object”,1=“Type”,2=“Company Name”,3=“ID”,4=“Name”,5=“Modified”,6=“Compiled”,7=“BLOB Reference”,8=“BLOB Size”,9=“DBM Table No_”,10=“Date”,11=“Time”,12=“Version List”;2000000009=“Session”,1=“Connection ID”,2=“User ID”,3=“My Session”,5="Login Time Any advice? Thanks.
So is your object table named ‘Object’? (Do SELECT TOP 1 * FROM Object). In many countries this and other system tables have been localized in the past and this is why the [identifiers] field is present. I cannot see why a ‘TableData not found’ for the Object table would occur otherwise. In the SQL solution this means that the table in SQL server does not have that name.
OK, at the end I created new database and import data from backup. I didn’t expect it for just one HotFix :(( And there is not any warning on Navision partnerguide web. My local test-DB is small, but what heppend when live DB is about 300 GB?
What I was driving at is that I have used the hotfix without problem, so the situation is not general and not expected. There should be no mention of it on partnerweb if others do not experience what you do.
Hi Robert, We have the same problem on a test system, where the user used a DE client to upgrade the database to hotfix 5. We now get the same error message as above. In our system we know for sure the DB was created with the W1 .stx file and upgraded with a DE .stx file. The object table in this database has a caption of Objekt, which presumably caused this issue. Any ideas as to how we could fix this? Not urgent, but certainly interesting… Regards Meint
Yes - this is now a known error related to the correlation between the localised texts in .stx file and the ‘Identifiers’ field of the [$ndo$dbproperty] tables, during the database conversion process. Anyway, Hotfix 12 of 3.70 fixes this issue. You should upgrade your database as it was prior to Hotfix 5 with hotfix 12 - i.e. do not use Hotfix 5 to upgrade at all.