Symptoms

You may see error messages  seeing the following error messages in K2 log files which are being em masse and clogging-up  "hostserverin" directory

Is it possible to get rid of those error messages or dicrease amount/frequency of those?

Sample error messages/log entries:

"Error", "GetUser:", "Resolving ForeignSecurityPrincipal (CN=). No attempts were made to retry."
"Error", "FindSecurityGroupsWithDefault:", "Resolving ForeignSecurityPrincipal (). No attempts were made to retry."
"Error", "GetUser:", "Resolving ForeignSecurityPrincipal (). No attempts were made to retry."
"Error", "GetDirectoryEntry", "The specified directory service attribute or value does not exist.
", " at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.RefreshCache()
at ADUM.K2UserManager2.GetDirectoryEntry(String path)", "Additional Information: ", "GetDirectoryEntry(LDAP://CN=ForeignSecurityPrincipals)"
"Error", "FindSecurityGroupsWithDefault:", "The specified directory service attribute or value does not exist.
", " at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne)
at System.DirectoryServices.DirectorySearcher.FindOne()
at ADUM.K2UserManager2.FindSecurityGroupsWithDefault(String User, String Name, String Description, String Email, String domainLDAP, String uOrgUnit)", "Additional Information: ", "ForeignSecurityPrincipals Resolve()"
 
 

Diagnoses

A Foreign Security Principal is required when expressing a relationship between groups in the local forest and security principals that exist across an external or cross-forest trust.
 

Resolution

You can enable the option to "Ignore Foreign Principals" in K2 Workspace under Management (Management Console) > tServerName] > User Managers-> K2 > Settings and the messages will no longer be logged in the ADUM log.
You will also NEED to restart the K2 Service in order for the change to be effected.