Dear all,
The situation: NAV 2009 R2, 2 localizations (BE and IT) are running on the same SQL server, 2 NAV servers are running to let the users connect to one and/or the other localization. (Also on the same machine).
The problem: While working in the classic client, when opening specific forms, reports, object designer, ... the "feared" error 47-1 appears.
I'm sure the fin.stx file is correct, because it is the same file that is used at other customers that have no problem with translations. But other customers only have one localization (in most cases BE). Does anybody have experience with running multiple localizations on the same machine?
The solution? I was thinking about using the W1 stx for resolving the issue, but as described in the problem I would like to hear your opinions first.
|Pressing F1 is so much faster than opening your browser||To-Increase| 0
Answers
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
To my knowledge this is the latest version of NAV.
This was not an upgrade but a new implementation.
|To-Increase|
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
The whole errors will be posted soon
opening object designer: There are errors in the text conversion because text no. 89-3257 does not exist in the .stx file.
Internal error: 47-1
right-click: There are errors in the text conversion because text no. 89-3229 does not exist in the .stx file.
Internal error: 47-1
Changing language to English:There are errors in the text conversion because text no. 1901-40 does not exist in the .stx file.
Internal error: 47-1
And something I've descovered while trying to summon the errors: when I change the language to NLB I can open the object designer. (this is a language not common to both localisations, and the program was initially installed from a NAVBE download. French is also a language not having the 47-1 error. So English and Italian remain.
|To-Increase|
By using the .stx and .etx files from the other localization (IT) the 47-1 error hasn't popt up since.
|To-Increase|
WOuld you please send me your .stx and .etx files?
I've copied from another marchine but it didn't work
Thanks in advanced!
I cannot send you the .stx and .etx file. But if you have the same error due to multiple localizations, I suggest you don't copy the .stx and .etx from another machine, but take the .stx and .etx from the localization you didn't use as base to install the NAV client/server/...
|To-Increase|
Please sog, it's not legislation, its localization.
If you find more misuses of the english language, please do not hesitate to point those out to me, a reaction however might stay out.
|To-Increase|
We use a 2009 R2 Build 34087 CC on SQL 2005.