<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

Code Fix: An error occurs when searching for a user and specifying a manager who does not exist

~~repeating-content.html~~
LEGACY/ARCHIVED CONTENT
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.

Issue Description

When using the User Manager (UMUser) SmartObject's Get Users method to search for a user in Active Directory, specifying a Manager name in the properties results in an Object Reference error logged in the Active Directory User Manager (ADUM) log file if the manager does not exist in Active Directory. The error message should state the manager could not be found.

Error Message

The error message displayed in the ADUM log file is similar to the following:

"Error", "FindSecurityUsersWithDefault", "Object reference not set to an instance of an object.", "   at ADUM.K2UserManager2.EscapeSearchFilter(String filter) at ADUM.K2UserManager2.FindSecurityUsersWithDefault(String Group, String Name, String Description, String Email, String Manager, String size, String domainLDAP, String upn, String uOrgUnit, String DisplayName)"

Resolution

  1. Ensure you have K2 4.7 installed.
  2. Download and Install the K2 4.7 March 2018 Cumulative Update from K2 Partner and Customer Portal.
  3. Get the K2 4.7 March 2018 Cumulative Update FP2 from Regional Support.
  4. Install the K2 4.7 March 2018 Cumulative Update FP2 to apply the fix.
  5. The correct error will now be visible in the ADUM log file with the following message:

The distinguished name property for the manager ‘{0}’ could not be found.