Internal Error 47-1 / Text missing in stx file

einsTeIn.NET

Hi @all,

I've got the same issue that is described in here http://www.mibuso.com/forum/viewtopic.php?f=23&t=45668.
But it doesn't get solved by the solution mentioned in that topic. Is there any other solution?

einsTeIn.NET

No one ever solved that issue? Is it possible that there are updates to stx files in hotfixes?

einsTeIn.NET

The answer is yes. There are update to stx and etx files. This hotfix (https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;EN-US;2496107) solves the issue.
The reason why this error occured was that we first installed 2009 SP1 and its language packs. When we update it to 2009 R2 we didn't realise that the language packs also need to be updated.

colingbradley

We have multiple SQL servers with multiple databases being accessed by people from all round the world, some using Navision 3.7 and some using NAV2009R2.
Some of the regional databases are in local languages.

My job is to be able to connect to many different databases and SQL servers to support them.

I just received the language for BE (.msi) and ran it.

Nothing seemed to happen and I was able to work OK.

Then rebooted the laptop and now I have this problem even though connected to a GB database.

I am working on getting access to the link but is the hotfix installed for each client?

einsTeIn.NET

Yes, you need to install the hotfix on every client.

I'm not sure what happened in your case, but I could imagine that the msi changed some registry key in background and now some of your installations refers to the wrong stx/etx files. Or maybe it replaced the stx/etx core files in your installation folder?

Anyway, this error mainly comes up when the NAV executables try to find a text reference in the stx/etx files but it can't find it. That means the referenced code no. is not in the files because they are either not up-to-date (e.g. wrong major version, wrong build) or they are of the wrong language. In second case you may also get some error message that says that the language of the license file doesn't match.

colingbradley

I sorted it by using the 'Repair' option from the installation disk.
Rebooted and all is now OK.
Obviously the language file I ran was changing the registry.