Resolve 'Failed to execute CreateUserEvent' Error: 'No items found' Due to LAH Definition Mismatch

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

When executing a custom task (based on CreateUser), the task fails with the error message: Failed to execute CreateUserEvent. The logs further report: No items found.

Environment

• Product: CA Identity Manager
• Version: 14.x

Cause

This error occurs when a Logical Attribute Handler (LAH) definition references a physical attribute that does not exist or has been incorrectly named. The Identity Manager engine attempts to resolve the attribute but fails because the referenced column is either misspelled or does not match the actual database schema.

Example error in logs: 2018-05-31 15:34:44,225 ERROR [ims.llsdk.directory.jdbc.jdbcbase] Failed to find managed object attribute definition for pivUsers.EmployeeAffiliation attribute

In this example, the LAH was configured to use pivUsers.EmployeeAffiliation, but the actual database column name is pivUsers.AdministrativeAffiliation.

Resolution

Follow these steps to identify and correct the LAH definition:

1. Analyze the Logs: Search your Identity Manager server logs for the error message Failed to find managed object attribute definition. Note the specific attribute path mentioned in the log (e.g., pivUsers.EmployeeAffiliation).
2. Verify the Attribute Name: Confirm the exact name of the physical attribute in your directory or database schema. Ensure that the name used in your LAH definition matches the schema exactly.
3. Update the LAH Definition:
   • Log in to the Identity Manager Management Console.
   • Navigate to your task configuration or the LAH definition set.
   • Replace the incorrect attribute name (e.g., pivUsers.EmployeeAffiliation) with the correct, verified column name (e.g., pivUsers.AdministrativeAffiliation).
4. Validate and Restart:
   • Save your changes to the LAH definition.
   • Restart the Identity Manager environment to ensure the new definition is loaded correctly.
   • Retest the custom task to confirm it now completes successfully.