This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Connect
- :
- FlexNet Connect Knowledge Base
- :
- Error When Registering Product with Client UI
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Error When Registering Product with Client UI
Error When Registering Product with Client UI
Summary
When registering a product on a non US English locale, an error stating "Couldn't find/load the 'locale' catalog for locale 'Symptoms
When attempting to register a new product/version on a machine where the system locale is not set to US English, an error stating: "Couldn't find/load the 'locale' catalog for locale '<system locale>' may be seen. This will be reported in a pop-up dialog which looks similar to the following:Cause
This will occur when the system locale is not set US English, and a localized locale.mo file can not be found matching the current system locale.Resolution
There are 2 ways in the Client UI to eliminate the locale error pop-up when registering:1. The quick way to override the default system language the Client UI is using for displaying the UI. When registering from the command prompt, it would be necessary to use "-l <languageCode>". The following command line illustrates: (-l 1033 indicates the US English language code):
FlexNetConnectClient.exe -r {9EEB8D54-EF35-416E-BD44-775252EBF5B8},1.05.201,1033 -ns http://updates.installshield.com
2. It is also possible to create a customized language strings for each supported locale. To do this, it would be necessary to create a directory matching the language code you wish to support, for example en_US, in the same directory as where you are running FlexNetConnectClient.exe, In this directory you would place a compiled locale.mo catalog, which would contain the customized language strings based on the locale. Refer to the README.locale in the Client UI kit (or the user manual) for directions on how to do this.
No ratings