Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Mixed language issue NAV2018 CU38 / CU47
rasmuwe
Member Posts: 4
Hello everyone,
We recently upgraded to NAV2018 (CU38) from NAV2016. On nav2018 we now have this issue with the system text being in "mixed translation" between english and danish (our language).
By system text I mean messages/errors that occur when you for example call:
or when you use:
The error message in the last example could be something like:
"Bilagstype must not be Tilbud in Købshoved: Bilagstype=Tilbud, Nummer="
(bold = danish, italic = english)
So the issue only exists with system text that you cant see/edit from C/SIDE or extensions. Multilanguage (ML Constants) works fine otherwise.
Anyone has a clue? We have tried many things: From changing/fiddling with server language and adjusting "Default Language" and "Services Language" properties on the NST.
Usually this just works though - without us doing anything. We tried upgrading to a newer CU (Now CU47) but problem persists.
We use Windows Server 2019.
We recently upgraded to NAV2018 (CU38) from NAV2016. On nav2018 we now have this issue with the system text being in "mixed translation" between english and danish (our language).
By system text I mean messages/errors that occur when you for example call:
Record.GET('something');
and no record were foundor when you use:
Record.TESTFIELD("Some field", "value");
and it returns an error.The error message in the last example could be something like:
"Bilagstype must not be Tilbud in Købshoved: Bilagstype=Tilbud, Nummer="
(bold = danish, italic = english)
So the issue only exists with system text that you cant see/edit from C/SIDE or extensions. Multilanguage (ML Constants) works fine otherwise.
Anyone has a clue? We have tried many things: From changing/fiddling with server language and adjusting "Default Language" and "Services Language" properties on the NST.
Usually this just works though - without us doing anything. We tried upgrading to a newer CU (Now CU47) but problem persists.
We use Windows Server 2019.
0
Answers
Thank you for your suggestion. We already looked in those files. Both are correctly translated to danish - also it seems like those files are alone for the integration development environment in NAV: C/SIDE. For example the error message for TESTFIELD could not befound in these files. Or maybe that is the problem? Does error messages for GET and TESTFIELD usually reside in these files - I cant seem to find them in my files. Can you check yours?
Nevertheless, in both installation folders you should have a folder named da-DK with several .resource.dll files. If you don't, you should re-install from a localized installation source (i.e. download the Danish DVD even for installing the platform files).
It won't hurt to do a repair installation anyways, unless you did not install using the installer in the first place. In that case you might be in all kind of trouble because of missing dependencies.
Thank you for answering. I already checked the language.ressource.dll files and they Seem correct. Under details I see language as danish. But naturally I cant look inside Them.
we installed from normal setup.exe on DVD.
We also tried repair but no difference.
Side note: We did make it work on one server though! but we dont know how.
We are currently having to clone this server when making new servers because new servers have the language issue!…
Maybe this information teels anyone something? I am sure it is server side as I tested from the same client connecting to two different servers, where one has the issue the other does not… It is very weird but maybe something stupid/simple…