The client uses custom cultures for some of their markets, for instance having CMS content for China in both Chinese [zh-CN] and English [en-CN]. However when we install the custom culture, en-CN, we get a 500 error as follows;
Event code: 3005 Event message: An unhandled exception has occurred. Event time: 5/12/2013 9:03:22 PM Event time (UTC): 5/12/2013 7:03:22 PM Event ID: 35dbcfc4a39844b299ad511121e5d340 Event sequence: 2 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/1/ROOT-1-130128589683037813 Trust level: Full Application Virtual Path: / Application Path: D:\Websites\www.client.com\wwwroot\clienttest.uk.episerverhosting.com\ Machine name: CLIENTTEST01 Process information: Process ID: 5016 Process name: w3wp.exe Account name: CLIENTTEST01\AgencyAdmin Exception information: Exception type: CultureNotFoundException Exception message: Culture is not supported.Parameter name: culture4096 (0x1000) is an invalid culture identifier. at System.Globalization.CultureData.GetCultureData(Int32 culture, Boolean bUseUserOverride) at System.Globalization.RegionInfo..ctor(Int32 culture) at Mediachase.Commerce.Currency..cctor()
Request information: Request URL: http://clienttest.uk.episerverhosting.com/IndexingService/IndexingService.svc/update/?accesskey=local Request path: /IndexingService/IndexingService.svc/update/ User host address: 127.0.0.1 User: Is authenticated: False Authentication Type: Thread account name: CLIENTTEST01\AgencyAdmin Thread information: Thread ID: 8 Thread account name: CLIENTTEST01\AgencyAdmin Is impersonating: False Stack trace: at System.Globalization.CultureData.GetCultureData(Int32 culture, Boolean bUseUserOverride) at System.Globalization.RegionInfo..ctor(Int32 culture) at Mediachase.Commerce.Currency..cctor()
Is there a way to successfully install a custom culture on Commerce 1R3?
This is a known problem, please get in contact with support and they will help you.
As Tobias noted, there is a known error with custom cultures and Commerce. There is a hotfix available now. You can request it via support.