up vote 2 down vote favorite
share [g+] share [fb]

I have a Classic ASP application running on a workstation with a Danish version of Windows 7 with IIS 7.5.

The problem: When the application writes a boolean as a string, it will write "True" or "False" on an English server. However, on my Danish installation, it will write out "Sand" and "Falsk".

The desired solution: What I need is to know which specific setting on my workstation/iis/configuration determines which language it writes out a boolean value to make sure it will always write out booleans in English.

I have tried the following already:

  • Set the LCID to 2057 (en_GB) for the ASP configuration of IIS.
  • Changed settings in Control Panel to English
    • Regional settings
    • Number and currency formatting
    • Language for non-Unicode programs
  • Changed the culture settings for ASP.NET in IIS
  • Restarted the workstation.

The following are not possible resolutions, so please don't suggest those:

  • Changing any code in the application.
  • Re-installing my workstation with an English version of Windows 7.
  • Changing the language of my Windows 7 installation (not possible because I am not using Ultimate and do not wish to upgrade)

Any suggestions will be appreciated. Thanks.

link|improve this question
I'm unsure about what to do with this question. I got good suggestions, but not the answer. Am I supposed to most useful answer anyway? – Niels Brinch May 31 '11 at 5:10
"choose the" fell out of my sentence above. Am I supposed to choose the most useful answer anyway? – Niels Brinch May 31 '11 at 5:56
feedback

2 Answers

up vote 1 down vote

I don't know that the old OLEAUT regional settings hack applies, but I think it's worth a try - see what you get.

http://support.microsoft.com/kb/271587

SetVarConversionLocale should be set to 2, and the default regional settings set to US English.

If that doesn't work, and you can't change code in your application, run a virtual machine with a US English OS. You didn't specifically exclude that :)

link|improve this answer
Microsoft state that the problem is only for Windows 2000 and that it was corrected in SP2 for Windows 2000, so I don't think that particular problem snugg back into Windows 7. The virtual machine idea is actually not all bad :) – Niels Brinch May 30 '11 at 3:22
The binary that includes support for the registry setting was included in Windows 2000 SP2. (that's the "fix" they're talking about, they're not saying "this problem goes away") I assume support for the registry setting has been carried forwards; as I said, it's worth a try. – TristanK May 30 '11 at 8:21
Ahh okay, that makes sense. Unfortunately adding those registry keys didn't make any difference. I tried all of them and tried setting them to both 1 and 2 without any different result. I ran an iisreset in between. – Niels Brinch May 31 '11 at 5:55
feedback
up vote 0 down vote

When you change regional settings in the control panel, you are doing this for your user profile; but IIS worker process usually run in other user contexts, depending on the configuration of the application pool(s). You should try changing the regional settings for those account(s).

link|improve this answer
I checked which application pool the website is using. I changed that application pool to identify itself as my own user account. I also tried with Network Service and "ApplicationPoolIdentity". It didn't work.Thanks for the suggestion, though- – Niels Brinch May 30 '11 at 3:14
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.