Hello, Lorenzo,

Glad to see you here! Happy new year!!

I'm almost fully confident that the following link will solve your issue:

https://dba.stackexchange.com/questions/172903/microsoft-sql-server-local-report-culture-is-not-supported-3072-is-invalide-cul

Can you please try to follow of one answers there? Very doubt that it is TBM problem.

Also, do you have second PC to test this? Or virtual machine, for example..

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!

Interesting! I've personally never needed to work with custom layouts, so can't comment on the solution, but absolutely great that finally this long-lasting problem is gone!!

Interesting! I've personally never needed to work with custom layouts, so can't comment on the solution, but absolutely great that finally this long-lasting problem is gone!!