Starting a process: Access denied (Turkish Execution Culture)

  • 16 February 2021
  • 0 replies
  • 1 view

Userlevel 4
Badge +18

Starting a process: Access denied (Turkish Execution Culture)


K2 blackpearl 4.6.11
K2 blackpearl 4.6.11
Contact Support KB
Code Fix
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 starting a new process, the following error may be shown:




If you look at your K2 Hostserver log files, more descriptive error messages may be shown:


"Access denied. You do not have permissions to perform this action or access this resources. Failed to initialize the Context: URL: https//[siteURL] username: Correlation ID: [correlationID] Error Details: Method: SharePointService.initializeContext"


The error above error was received even though the user has sufficient rights.


A second error may appear: 

"24408 K2:Domain[AccountName] from [IP] does not have rights to start Process [ProcessName]"


If you grant "start" rights to the K2 application pool account, this will allow you to to start the workflow, but the record will be saved as the application pool account instead of the currently logged in user. 




Our developers identified this only happens to users from the Turkey region, as the issue relates to the Turkish culture within the K2 Product.


The issue has been resolved in K2 4.7 and onwards. However, if you experience this issue in K2 4.6.11 please contact K2 Support for this codefix.

0 replies

Be the first to reply!