Possibly a Courier issue, but our Culture Picker is somehow getting the wrong language identifier to the system.
Please help! This is happening on our staging and production servers. Any ideas?
Stack Trace:
Culture is not supported. Parameter name: name English (Canada) is an invalid culture identifier.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Globalization.CultureNotFoundException: Culture is not supported. Parameter name: name English (Canada) is an invalid culture identifier.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[CultureNotFoundException: Culture is not supported.
Parameter name: name
English (Canada) is an invalid culture identifier.]
System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride) +256
System.Globalization.CultureInfo.CreateSpecificCulture(String name) +6475565
Applied.Global.setLocale() in C:\Users\bhill\Documents\AppliedSystemsUmbracoExtensions\AppliedSystemsUmbracoExtensions\AppliedSystemsUmbracoExtensions\Global.cs:103
Applied.Global.Application_PreRequestHandlerExecute(Object sender, EventArgs e) in C:\Users\bhill\Documents\AppliedSystemsUmbracoExtensions\AppliedSystemsUmbracoExtensions\AppliedSystemsUmbracoExtensions\Global.cs:42
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +80
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
For anyone seeing this, turns out the Value of the Drop Down list has the incorrect values in them. instead of value="en-US" they are like value="English (United States)" Which, when the node is saved is entered into the database and then causes the error. Trying to determine how that happened still. The fix was to change the database values to what they were supposed to be and then republish the site.
Site language Key suddenly changed to English (United States)
Possibly a Courier issue, but our Culture Picker is somehow getting the wrong language identifier to the system.
Please help! This is happening on our staging and production servers. Any ideas?
Stack Trace:
Culture is not supported.
Parameter name: name
English (Canada) is an invalid culture identifier.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Globalization.CultureNotFoundException: Culture is not supported.
Parameter name: name
English (Canada) is an invalid culture identifier.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace:
For anyone seeing this, turns out the Value of the Drop Down list has the incorrect values in them. instead of value="en-US" they are like value="English (United States)" Which, when the node is saved is entered into the database and then causes the error. Trying to determine how that happened still. The fix was to change the database values to what they were supposed to be and then republish the site.
is working on a reply...