ASP.NET AJAX Discussion and Suggestions

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Tue, 26 Sep 2006 18:06:15 GMT

hello.

well, i really don't think this is the case. what's happening here is that the browser is sending the wrong culture string (well, at least that's what i think) and that is breaking the atlas globalization handler.

Re: Culture name 'en_us' is not supported. Parameter name: name

TRocca — Mon, 25 Sep 2006 23:20:06 GMT

It is very likely that doing your testing you enabled the personalization for grasping the user preferences, in that case I would check if you do not have a wrong Culture definition stored there i.e. "en-UK" instead of "en-GB"....

Try to force in your InitializeCulture method something like LanguagePreference = "en-GB" just before the

this.Culture = LanguagePreference;

this.UICulture= LanguagePreference;

it should work, then force a change in the Culture so that the right value gets stored in the personalization database....

Doing a rapid checking in the watch window while breaking one step before the assignment you will be able to see what you are trying to push there... it is likely crappy :-)

Hope it helps

TRocca

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Thu, 07 Sep 2006 22:49:01 GMT

hello again...as you've noted i've completly forgot to answer...after using opera, i've notice that it's sending stange combinations for the current culture (en_us instead of en-us). i was under the impression that en-us is correct. am i wrong?

Re: Culture name 'en_us' is not supported. Parameter name: name

kerry-jiang — Thu, 07 Sep 2006 05:55:05 GMT

Luis Abreu:

hello.
hum...if i recall correctly, atlasglob.axd injects the current culture on the page. i'm downloading your sample to see if i can get it to work (though i really think i won't be able to do anything about it). btw, are you using any globalization features? if not, i think that disablling it through the scriptmanager will make the problem go away (without solving it).
btw, any specific configuration needed to reproduce this with opera? (i'm downloading it now)

Thanks your this reply, I have resolved this problem by adding a property EnableScriptGlobalization="false" to ScriptManager!

Re: Culture name 'en_us' is not supported. Parameter name: name

Janh — Wed, 30 Aug 2006 18:13:00 GMT

Luis Abreu:

hello agian.
well, but what kind of culture is rs1_39....? I mean, the atlasglob could be changed so that i catches the exception...but i do really think that the name of the culture is wrong (btw, what culture does it represent?). as i said in previous posts, atlas uses .NET culture classes to build the jscript object which is passed along to the client. if you really do think that the culture is correct (which i really doubt), then you can build your own handler which mimics the default behavior of the atlasglob.axd handler but returns the correct result(use reflector to get a feeling for the internal code used by the default atlas globalization handler).

Let's not only talk about the rs1..... cultures, which I don't know what is it either. Let's consider other ones we talked about, such as zh, zh-hk, zh-tw (Chinese), zu (Zulu), nb (Norwegian), and last but not least en_us (English!). All these exist yet atlas throws exceptions.

I don't want to build a handler. This shouldn't even be happening. Say even if the culture that the user's browser pass in isn't correct, shouldn't atlas just continue to work?

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Sat, 26 Aug 2006 22:31:21 GMT

hello agian.

well, but what kind of culture is rs1_39....? I mean, the atlasglob could be changed so that i catches the exception...but i do really think that the name of the culture is wrong (btw, what culture does it represent?). as i said in previous posts, atlas uses .NET culture classes to build the jscript object which is passed along to the client. if you really do think that the culture is correct (which i really doubt), then you can build your own handler which mimics the default behavior of the atlasglob.axd handler but returns the correct result(use reflector to get a feeling for the internal code used by the default atlas globalization handler).

Re: Culture name 'en_us' is not supported. Parameter name: name

Janh — Sat, 26 Aug 2006 00:46:01 GMT

Yes, that is happening on my site too. IE throws errors on other languages but works fine when it comes to English. I get lots of:

Culture name 'zh' is not supported. Parameter name: name
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Culture name 'rs1_3966f6badce' is not supported. Parameter name: name
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 55SP1D11262000R5; YPC 3.0.1; SV1; .NET CLR 1.0.3705; yplus 4.1.00b)

Culture name 'ie-ee' is not supported. Parameter name: name
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

Mozilla is no exception either.

Months passed and still no answer. This is really frustrating.

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Thu, 10 Aug 2006 21:41:53 GMT

hello again.

well, check the string that is being passed and see if it has a valid value.

Re: Culture name 'en_us' is not supported. Parameter name: name

kerry-jiang — Thu, 10 Aug 2006 03:40:32 GMT

But the file atlasglob.axd also throw this kind exception when I using Chinese Version Internet Explorer not use opera, Is it a bug of Internet Explorer to send wrong culture string ?

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Wed, 09 Aug 2006 20:03:56 GMT

hello.

well, it's not an atlas bug. in fact, if you use globalization on an asp.net site, I think you'll have the same problems. the problem is that opera is sending en_us instead of the en-us (and I really think that en-us is the correct option, though I may be wrong...)

Re: Culture name 'en_us' is not supported. Parameter name: name

kerry-jiang — Wed, 09 Aug 2006 08:47:33 GMT

But why so many culture could not be supported, it should be a bug of ATLAS!

Who has a efficient method to solve this problem?

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Mon, 31 Jul 2006 21:46:12 GMT

hello.

though i'm no globalization guru, i think that this depends on the code you're using. if i recall correctly, only the localeXXX methods use that info (ex.: string.localeformat). if you look at the source file, you'll note that there's a sys.cultureinfo object introduced by default (en-us). when you use the atlas globalization handler, it tries to override that object with the current culture. you're getting the error because the brwoser is sending invalid cultures (in .net, the culture must be called en-us; not en_us. I was under the impression that using the globalization element would solve this, but it seems like it doesn't - i'll try to investigate what's going on and if i find anything i'll post back).

Re: Culture name 'en_us' is not supported. Parameter name: name

Janh — Mon, 31 Jul 2006 21:31:29 GMT

Thanks for taking a look at it.

I didn't do anything special, just downloaded Opera 9 and was able to reproduce this error immediately on my site.

Any problem if I disable the globalization features? Quite a few foreign-language users visit the site (where I get 'zh' is not supported, 'mi-nz' is not supported and a bunch of 'rs1_*' is not supported), would that affect them?

Thanks again!

Re: Culture name 'en_us' is not supported. Parameter name: name

Luis Abreu — Mon, 31 Jul 2006 20:46:09 GMT

hello.

hum...if i recall correctly, atlasglob.axd injects the current culture on the page. i'm downloading your sample to see if i can get it to work (though i really think i won't be able to do anything about it). btw, are you using any globalization features? if not, i think that disablling it through the scriptmanager will make the problem go away (without solving it).

btw, any specific configuration needed to reproduce this with opera? (i'm downloading it now)

Re: Culture name 'en_us' is not supported. Parameter name: name

Janh — Mon, 31 Jul 2006 20:39:27 GMT

Sorry for the confusion, that was a major typo. I meant "en_us" and not "en-us", underscore and not hyphen.

Anyway, I made an empty atlas webapp:

http://38.101.169.95/default.aspx (calls a web service returns “Hello World”)
http://38.101.169.95/default2.aspx (an empty script manager)
http://38.101.169.95/ErrorLog.txt (I write HttpContext.Current.Server.GetLastError().GetBaseException() to this text file, with errors Culture name 'en_us' is not supported.)

Both of these work on IE and FireFox, but when using Opera 9, I get the following javascript error that includes JavaScript - http://38.101.169.95/atlasglob.axd Linked script not loaded. This problem causes the whole page unable to use Javascript, and of course, Atlas.

JavaScript - http://38.101.169.95/default.aspx
Inline script thread
Error:
name: TypeError
message: Statement on line 25: Type mismatch (usually a non-object value used where an object is required)
Backtrace:
Line 25 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghNU3WBmaCNx7V-W0WWPHF2g2&t=632870166220000000
    w.HTMLElement.prototype.__defineGetter__("children", (function ()
{
var elementNodes = [];
var childCount = this.childNodes.length;
for (var i = 0;i < childCount;i++)
    {
      var childNode = this.childNodes[i];
      if (childNode.nodeType == 1)
        {
          elementNodes.add(childNode);
        }
    }
return elementNodes;
}
));
w.HTMLElement.prototype.__defineGetter__("innerText", (function ()
{
return this.textContent;
}
));
Line 92 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghNU3WBmaCNx7V-W0WWPHF2g2&t=632870166220000000
    _loadMozillaCompatLayer(window);
JavaScript - http://38.101.169.95/atlasglob.axd

Linked script not loaded
JavaScript - http://38.101.169.95/default.aspx
Event thread: load
Error:
name: TypeError
message: Statement on line 455: Could not convert undefined or null to object
Backtrace:
Line 455 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghf7DMx5_wA-Q1&t=632870166220000000
    var scriptDOM = new XMLDOM(scriptMarkup);
var scriptDocumentNode = scriptDOM.childNodes[0];
scripts.add(scriptDocumentNode);
Line 504 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghf7DMx5_wA-Q1&t=632870166220000000
    Sys.Runtime.load.remove(onRuntimeLoad);
Sys.MarkupParser.processDocument(_markupContext, onLoaded);
Line 243 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghf7DMx5_wA-Q1&t=632870166220000000
    for (i = 0;i < handlers.length;i++)
          Line 263 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghf7DMx5_wA-Q1&t=632870166220000000
    if (_initialized == false)
      Line 268 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghf7DMx5_wA-Q1&t=632870166220000000
    Sys.Runtime.initialize();
Line 16 of linked script http://38.101.169.95/WebResource.axd?d=Bht-lwqvmfjldSfYDM5-qKNfp0213N7ob0r9V8JJda7eb8gKfw8y9BzcQsyPXQFeSRpjo1niStQgH2MAll0hBx15VCMLzxghNU3WBmaCNx7V-W0WWPHF2g2&t=632870166220000000
    window.event = e;
eventHandler();
return e.returnValue;
At unknown location
    [statement source code not available]

http://38.101.169.95/Atlasglobaxd.rar (my source files)