Skip to main content

We are trying to migrate a huge application into Production that has been tested in 2 different environments using AD Groups.  When we are migrating to our Production Environment we are getting the error of 64007","IdentityServiceError","IdentityService.ProviderCacheIdentity:RoleProvider.GetUser","

Our Tasks are being sent to AD Groups with multiple names in them.  We are not using roles as this would require 500+ with the amount of different approval steps.

 

This is working in 2 other environments BUT our Production.

 

Any Suggestions?    Needing something to look into fast since this is going live tomorrow.

Hello  @AAschenbrener, 


 


There are two things that you might look into to see if they are causing this. 



  • Check your AD groups. Are any of them disabled that are showing in the errors? If so, please enable the group(s). 

  • Check the Adum logs on your server (C:/Program Files/K2/Host Server/Bin/AdumErrorxxxxxx_x.log), are there any errors that look like, "Failed to translate name"? If so, it is likely that the group name contains a special character that it should not such as @, #, ect. Renaming the group  to exclude the special character should resovle this if this is the case. 


Hopefully these help or at least point you in the right direction! 


 


Thanks, 


Samuel 

Ending up finding that in the Workflow we changed the Task Notification Recipient to 'Group' instead of User for the that particular Environment.  

 

It was very weird that it was working in different environments but after working with the K2 Support team we found the solution.

 

Thank you!!

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings