I am running a site using en-gb but for some time I have had to reset the language to en-us if I want to edit anything, otherwise I get teh "object reference" error.  However I now find that I cannot access the "Languages" module to reset it.  The message I am getting is:

DotNetNuke.Services.Exceptions.ModuleLoadException: Culture ID 2155 (0x086B) is not a supported culture. Parameter name: culture ---> System.ArgumentException: Culture ID 2155 (0x086B) is not a supported culture. Parameter name: culture at System.Globalization.CultureTableRecord.GetCultureTableRecord(Int32 cultureId, Boolean useUserOverride) at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride) at System.Globalization.CultureInfo..ctor(Int32 culture) at System.Globalization.CultureTable.GetCultures(CultureTypes types) at DotNetNuke.Services.Localization.Languages.LoadLocales() at DotNetNuke.Services.Localization.Languages.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

The dnn version 04.03.04.  I was hoping to upgrade but am reluctant to do so with this error in place.

Grateful for any advice.

as per http://msdn2.microsoft.com/en-us/library/system.globalization.cultureinfo.aspx 0x086B is not a standard Culture Identifier.

i did a quick search and found this thread on the msdn forums: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1794370&SiteID=1

I really hate to revive SUCH an old thread, but I just encountered this error running DNN 4.8.4.

I'm assuming it's a hosting issue. I have a coupe sites with the same host (based on the same account) and they both give me this error when I go to Admin->Languages.

I uploaded 1/2 dozen or so modules that I was upgrading and when I was going through checking them one came up with the error

"Cannot create an object of type 'System.Globalization.CultureInfo' from its string representation 'English (United States)' for the 'Culture' property."

There's a little more to it, but it's just the stack trace back to InjectModule.

I've sent my host all the information from this thread and they are looking into it, but I was just wondering if anyone had any new pointers? I've noticed that the information about this error seems a little 'old', like this thread *smiles* but figured maybe someone at some point came across it and can offer something new?

Many Thanks.