When running a Directory Connector configured to process specific object types (e.g., Resources, Mailin databases), the following error appears in the logs:
Unable to find object type for AD search result
This issue typically arises during the synchronization of mail-in database entries when the connector encounters an unexpected object type in Active Directory.
The connector is encountering an AD object that is classified as a Group (sometimes with a naming prefix).
However, the connector configuration is explicitly set not to process group objects — only resources are enabled in the SyncConfiguration
block.
As a result, the connector fails to resolve the object type and defaults to provisioning a new contact instead, which may not be the desired behavior.
Identify the Object Type:
Confirm that the object returned by the AD search is a Group and not a User or Resource. This can typically be seen by naming conventions or by querying AD directly.
Review Connector Configuration:
Check the connector configuration file and verify the enabled object types. In this case, groups were intentionally excluded.
Customer Action Required:
If group processing is not intended, the AD must be cleaned up by the customer to remove or reclassify objects that conflict with the connector’s scope.
Optional – Modify Configuration (if applicable):
If the group objects should be processed, update the connector configuration to include groups by setting the relevant flags to true
.
Additional Notes:
This is a configuration-based issue and not a defect in the connector logic.
No changes are required from Quest if group processing is not intended.
The customer is responsible for ensuring the AD structure aligns with the connector’s configuration scope.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center