Unable to contact connector to generate unique value and is not retry-able - error

[rt111 (Ricardo Then)]

Hello,

I noticed that there are 5 identities within my organizations IDN solution that are having issues being processed, and as a result, are not being created within local AD. The error (screenshots attached) states that it is unable to generate a unique value for it. I am not entirely sure what is the proper way to fix this, and I was wondering if anyone around here ran into a similar issue, and if so, what steps you took to fix it.

As far as I am aware, we don’t have any low DNs limits within our local AD. The SamAccountName for the 5 users is 20 characters or less. We haven’t had any issues creating local AD accounts with the DNs format that these 5 accounts would be using (e.g., DN=USERNAME,OU=Users - Double Enrollment,OU=DOMAIN Users,DC=SERVER,DC=NAME).

I confirmed that no other account exists with the usernames of these 5 users, and they are unique. This include local and Azure AD (IDN is configured with both sources, but only configured to create accounts within local AD).

Per another user’s recommendation:

Getting error during AD creation

Hi Team, I’m getting error during Creation of AD below is the error . Please find below error for ref. Error generating a unique value, the exception was: java.lang.Exception: Unable to contact connector to generate unique value and is not retry-able. Action:UniqueAccountIdValidator: Calling getObject for objectType ‘account’ using id ‘CN=testfn102, testln10249 (sbs999952),ou=users,ou=TCS,ou=hospitals,ou=sb-departments,dc=XXX,dc=’ and options ‘{cloudConfigOverrides={aggregateTimeout=30, disa…

I checked the cloudMaxSize for the local AD create account source, and the only thing that I found that matches that is this:

"attributes": {
                "template": "$(username)",
                "cloudMaxUniqueChecks": "50",
                "cloudMaxSize": "20",
                "cloudRequired": "true"
            },

This seems normal as it matches the local AD SamAccountName limit of 20 characters (unless I am misinterpreting this).

Weirdly enough, the error makes reference to the Azure AD source, which I am not fully sure as to why since we don’t create accounts on that source. I also did a test connection to the source, which was successful.

Thank you in advance for your help.

Sincerely,
Ricardo T.

[phil_awlings (Phil Rawlings)]

hi @rt111

I used to get this error through bad correlation. Sometimes the .2 accounts would create fine, but correlate to the .1 accounts. Have you checked other accounts with the same name but different counter numbers?

Phil

[rt111 (Ricardo Then)]

Hi Phil,

I did, but I don’t see any other accounts with similar name.

Thank you,
Ricardo T.