Error encountered "The culture information failed to load [500] Internal Server Error" when trying to edit a View

  • 24 February 2022
  • 0 replies

Userlevel 4
Badge +17

Error encountered "The culture information failed to load [500] Internal Server Error" when trying to edit a View


K2 blackpearl 4.7
K2 smartforms 4.7
K2 smartforms 4.7
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


When attempting to edit a View from K2 Designer, the error below appears and the View continues to spin infinitely.


"The culture information failed to load [500] Internal Server Error (error)"




  • To debug your web page, run a fiddler trace or a network trace using F12 Developer Tools from your browser while reproducing the issue, you should see a HTTP/1.1 500 Internal Server Error returned.
  • From the Web View of the erraneous request, it shows a configuration error 'Cannot add duplicate collection entry of type 'add' with combined key attributes 'users, roles, verbs' respectively set to DomainUserName'. If you look at the Config Source, it points to the authorization rules configuration in the K2 Designer web.config file.


Troubleshooting Steps

To verify and resolve the issue, kindly perform these steps:


1. Edit the K2 Designer web.config file (usually located in C:Program Files (x86)K2 blackpearlK2 smartforms Designer), find the section below and check if the AccessType configuration is assigned to each user separately.


An example:

<add accessType="Allow" users="DomainUser" />
<add accessType="Allow" users="DomainUser" />
<add accessType="Allow" users="DomainUser" />


2. If so, merge all the users with a comma separation into 1 line of <add accessType="Allow"


For example:


<add accessType="Allow" users="DomainUser,DomainUser,DomainUser" />
Please remember to create a backup of the web.config file prior to making any modification.

3. Save and close the file.


4. Then, perform an IISRESET.


5. Try editing your View again. The error should disappear. 


0 replies

Be the first to reply!