Trados Business Manager – End of Life Announcement

Trados Business Manager (TBM) has reached end of life. Following the discontinuation of TBM sales on 31 October 2023, all maintenance and support services will conclude on 31 October 2024.
What Does This Mean for TBM Users?

  • End of Services: RWS will no longer provide any services related to the installation or updating of TBM.
  • Existing Installations: TBM will remain functional where already installed, but the RWS support team will not offer assistance in troubleshooting issues, addressing reported problems, or providing further development for TBM.
  • Documentation: The TBM documentation has been removed from docs.rws.com.
  • Community Support: The community forum for TBM will remain accessible in a read-only format for users to reference if needed.
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 8 subscribers
  • Views 2507 views
  • Users 0 members are here
Options
Related

Problems with "Invalid Culture Identifier"

Lorenzo Martinelli

Hi Eugene!

Happy new year!

I just discovered that BaccS has become SDL Trados Business Manager.

So, I went ahead and I installed it afresh on top of the original BaccS 5 installation (I was not entirely sure how the licensing worked, so I wanted to prevent hassles)

However, the issue with the invalid culture identifier continues. When I click on Instructions, or I try to change a QuickReport the message appears

Error message in SDL Trados Business Manager stating 'Culture is not supported. Parameter name: culture 3072 (0x0c00) is an invalid culture identifier.'

What is baffling is that the culture that SDLTBM gripes about is not the culture the PC is set to (as you can see in the screenshot below)

Command prompt showing the system culture set to 'en-GB' with LCID 2057, Name 'en-GB', and DisplayName 'English (United Kingdom)'.

I’d appreciate any idea you might have

Lorenzo

Generated Image Alt-Text
[edited by: Trados AI at 5:28 AM (GMT 0) on 5 Mar 2024]
emoji
Rate translation
×
Suggest better translation
×
Parents Reply
  • 0 in reply to Eugene Kuchynski

    Hi Eugene!

    So I fired up a VM, and installed a demo of SDLTBM and lo and behold the problem was not there.

    Eventually, I realised that the main, language related, difference between the two was the keyboard layout.

    The main machine has a custom keyboard layout created eons ago with Microsoft Keyboard Layout Creator.

    When I uninstalled that layout, SDLTBM worked fine.

    I then created and installed a new keyboard layout, which worked fine, so I went to HKLM\SYSTEM\CurrentControlSet\Control\Keyboard Layouts to discover which was the faulty layout .dll, and finally I deleted the faulty layout DLL it from C:\Windows\System32

    How that layout got corrupted beats me, but there you go.

    All the best!
Children