Follow the steps listed here to troubleshoot if an EntityNotFoundException occurs when you are trying to get the current members of a group in a database repository with cross-repository configuration.
Virtual member manager does not return the current member results for a group in a database repository, if a user who was a member of this group was previously deleted from an LDAP repository. Instead an EntityNotFoundException is thrown.
This problem occurs because the group membership of non-existing members is not deleted from the database repository when its members in an LDAP repository are deleted.
Follow the procedure given next to define the repositoriesForMemberDeletion custom property in the database repository where the group exists and specify the LDAP repositories of the non-existent members whose group membership you want to be deleted.
You must also apply the WebSphere Application Server 7.0.0.17 fixpack or above. (For WebSphere Application Server version 6.1, you must apply the 6.1.0.39 fixpack or above.) After you apply this fixpack successfully, the next time that you search for group members, the group memberships of all the non-existent members are removed from the group. Searching for members of the group displays the remaining group members and EntityNotFoundException does not occur.
$AdminTask setIdMgrCustomProperty { -id "DBRepoID" -name "repositoriesForMemberDeletion" -value "TDS;AD" }