Written by Gibran
July 30, 2020
We recently had a problem with a vendor software and it took us considerable time to find the solution. The problem was as follows:
- The application is installed on a Windows Server 2008 R2 to which we connect via remote desktop connection to support it.
- Proxy connection parameters need to be configured.
- When we put the cursor on any Input Text Field and press any key, the program crashes.
Of course we attributed the problem to the application and the vendor attributed it to the hardware. Thank God, a colleague diligently reviewed the application logs in the Event Viewer and encountered the following error:
Culture is not supported.Parameter name: culture22538 (0x580a) is an invalid culture identifier.
We did a quick search and found the following entry, which already offers a solution that could serve several: LINK
As the author of the post explains, Culture 0x580a means es-419 or Spanish (Latin America). The program crashes because my physical keyboard is configured in that language but the server does not have it installed.
We therefore tried to install the language on the server but it was not possible because of network restrictions, so I chose to change the keyboard language of my local computer. But maybe because of corporate restrictions, I couldn’t change it either.
The solution.
Finally, my solution was to use the server’s on-screen keyboard to enter the required parameters. It worked for me and the problem was solved.
Conclusion :
If you don’t need to enter information frequently on the server or just want to avoid going through the process of adding a language or changing the language of your keyboard, use this solution. Simply use the screen keyboard, pressing win +R and typing “osk”.
I send a greeting to Tomas Restrepo, who thanks to his entrance we hit the nail on the head without much complication.
Peace and good!