No ratings

"Failed to resolve 'K2:THEDOMAIN\THEGROUP: Group cannot be found" exception appears when resolving AD Group


"Failed to resolve 'K2:THEDOMAIN\THEGROUP: Group cannot be found" exception appears when resolving AD Group

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 issue occurs when you have a group provider that has the same name as a domain. This results in a csom code path being taken vs directory services which results in the following stack trace:

"77888184","2018-07-25 21:20:19","Error","General","0","ErrorMessage","1","0 SharePointRoleProvider.GetGroups: System.Reflection.TargetInvocationException: An unexpected failure was encountered when contacting SharePoint to get information from the group provider Headquarters: Group cannot be found. ---> System.Exception: Group cannot be found. at SourceCode.SharePoint15.Client.CSOMFunctions.GroupFunctions.LoadGroup(Group group, Boolean throwException) at SourceCode.Security.Providers.SharePoint.Shared.SPCsomClient.SourceCode.Security.Providers. SharePoint.Shared.ISPGroupProviderClient.GetGroup(String groupName) --- End of inner exception stack trace ---","anonymous","","SRVRVM-K2Web01:C:\Program Files (x86)\K2 blackpearl\Host Server\Bin","77888184","7550335abdef4a7caf65343fc75eba69","" "77888185","2018-07-25
21:20:19","Error","IdentityService","64005","ResolvingException","IdentityService.ProviderCacheIdentity: GroupProvider.GetGroup","64005 Failed to resolve 'K2:THEDOMAIN\THEGROUP: Group cannot be found..","anonymous","","SRVRVM-K2Web01:C:\Program Files (x86)\K2 blackpearl\Host Server\Bin","77888185","3c460ce1b87541b7a3803ec9d83e680c",""



The symptoms of this issue consists of lost membership as well as the group being disabled. Also, explicitly resolving the group via the tester results in the lack of ADUM logs. This is a red flag for this issue as it proves directory services is not being hit.


To resolve this issue, delete the problematic group provider and rename the site. Once remapped to K2, the issue will not persist.


To delete a Group Provider, navigate to K2 Management site > Users > SP:



Labels: (1)
Version history
Last update:
‎05-19-2021 08:08 PM
Updated by: