I keep getting this error on my site.  Any advice on how to fix this issue?  I'm using the June CTP.

Error in:	http://www.mysite.com/atlasglob.axd
Error Message:	Culture name 'en_us' is not supported. Parameter name: name
Referring Page:	http://www.mysite.com/content/support/FAQ.aspx
Stack Trace:	at System.Globalization.CultureInfo.CreateSpecificCulture(String name) at Microsoft.Web.Globalization.AtlasCultureInfo.Create(String cultureName) at Microsoft.Web.Globalization.GlobalizationHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 

 

I have the same exact problem.  I see this error using April CTP and the error still exists when I upgraded to June CTP.

Not only I see 'en_us' is not supported, I also see a lot of

 Culture name 'rs1_e554ec67d1a' is not supported. Parameter name: name

I couldn't find any help on this.  My site doesn't have any foreign language support either, so is this trying to tell me that I need to?

Will any MS rep comment on this? This is a huge problem and is causing AT THE LEAST 200 unhandled exceptions per day on our server.

My attempts to solve this problem have included setting the globalization in web.config as such...

<

globalization uiCulture="en" culture="en-us" requestEncoding="utf-8" responseEncoding="utf-8" />

attempting to override the current thread's culture property and attempting to override the Culture property for the Request object. All of these have failed.

Come on guys, let's at least have a comment that you know the problem exists.

I'm also getting thousand of this exceptions every day... :(

andrew_:

<

globalization uiCulture="en" culture="en-us" requestEncoding="utf-8" responseEncoding="utf-8" />

Shouldn't it be en-US? i seem to recall having seen a classic ASP.NET globalization problem a long time ago which was caused by using us instead of US...

Same problem here, with a lot of different cultures.
Is there a solution to this problem?

Does this help any?

Culture name 'mt-mt' is not supported. Parameter name: name

Source:

mscorlib > System.ArgumentException > CreateSpecificCulture

Filename:

http://www.mydomain.com/atlasglob.axd

Stack Trace:

at System.Globalization.CultureInfo.CreateSpecificCulture(String name) at Microsoft.Web.Globalization.AtlasCultureInfo.Create(String cultureName) at Microsoft.Web.Globalization.GlobalizationHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

------------------------------

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

Culture name 'rs1_8dd96e8ec14' is not supported. Parameter name: name

Culture name 'rs1_5110543227a' is not supported. Parameter name: name

Culture name 'mi-nz' is not supported. Parameter name: name

Culture name 'rs1_72ad19e9147' is not supported. Parameter name: name

Culture name 'zh_tw' is not supported. Parameter name: name

Culture name 'rs1_8419976a4ca' is not supported. Parameter name: name

---------------------------------

Though not sure if it's related, not all but most of Culture name 'en_us' is not supported. Parameter name: name have

User Agent:

Opera/9.00 (Windows NT 5.1; U; en)

Given that Opera is less than 0.1% of our user base but they show up quite often in this case.

And for Culture name 'us' is not supported. Parameter name: name

User Agent:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060326 Firefox/1.5.0.3 (Debian-1.5.dfsg+1.5.0.3-2)

And for Culture name 'rs1_*' is not supported. Parameter name: name

User Agent:

Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)

User Agent:

Mozilla/4.0 (compatible; MSIE 6.0; AOL 9.0; Windows NT 5.1; .NET CLR 1.0.3705)

User Agent:

Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; YPC 3.0.3)

 

Luis Abreu:

Shouldn't it be en-US? i seem to recall having seen a classic ASP.NET globalization problem a long time ago which was caused by using us instead of US...

.NET will parse that correctly despite the case of the letters. Did some testing on that as well. Despite this fact, changing the culture in web.config did little to help. I even tried changing the language setting in the browser manually to en-us, which solved the exception about the cultures, but ATLAS then throws a series of javascript errors that I'm unable to track down, or find a workaround with.

I never thought I would be an open source advocate, but this could REALLY benifit from some community help.

hello again.

hum...interesting...if you look in google, you'll see that several guys say they're different (maybe that changed in this version?). oh well, you got me curious...can you build a small site that reproduces that and send it to me?

I'm running June CTP.

I can repro the bug easily on one of sites (http://www.thebearmill.com/thebearmillstore_bears.aspx).

Simply open IE6, Toosl, Internet Options, General, Languages.

Remove anything from there, add a user-defined 'asdf' or anything (I got this error for ru_ru on my site), go to the site and navigate.

If you try to click on add to cart, the error will be thrown server-side and you'll see a JavaScript error.

 

Exception occurred -

http://www.thebearmill.com/atlasglob.axd

Exception: System.ArgumentException

Message: Culture name 'asdf' is not supported.

Parameter name: name

Source: mscorlib

at System.Globalization.CultureInfo.CreateSpecificCulture(String name)

at Microsoft.Web.Globalization.AtlasCultureInfo.Create(String cultureName)

at Microsoft.Web.Globalization.GlobalizationHandler.ProcessRequest(HttpContext context)

at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

 

 

 

 

andrew_:

My attempts to solve this problem have included setting the globalization in web.config as such...

<globalization uiCulture="en" culture="en-us" requestEncoding="utf-8" responseEncoding="utf-8" />

attempting to override the current thread's culture property and attempting to override the Culture property for the Request object. All of these have failed.

Come on guys, let's at least have a comment that you know the problem exists.

That's because this get's the culture info from the browser header...
I'm having this error since i added the section

<add verb="*" path="atlasglob.axd" type="Microsoft.Web.Globalization.GlobalizationHandler" validate="false"/>

hello guys.

i still think that this is related with using an invalid culture string.

btw, i think you can disable gloalization by setting the enablescriptglobalization property of the scriptmanager class to false...

Of course invalid culture strings should cause errors.

However, this brings up the following question:

What does ATLAS need globalization for?

Isn't just ATLAS a behavioural library? What behaviour changes when you change locales?

Jason

If ATLAS does indeed need globalization, and it does indeed need to throw some kind of error, then I would think that it would be more useful to throw a warning of some sort and then default to a language locale that wouldn't fail, taking down the application. If a user alters his browser settings to something custom which .NET doesnt agree with, it should definately catch this error and default to a safe setting.