Specific user cannot be added to Security Users from Windows AD

[PeteC]

I am trying to enable user security on a model (EAPX file). On the model that I want to enable security, I can add myself and some other users, but one specific user, while found in the directory within the Import Users dialog, when the desired Security Group is selected and Import clicked they do not appear in the list of users. I can find other users who I can also not import, so multiple users are OK and multiple users are not OK. I have browsed to the same location within the directory so it should not be related to being an account in a different part of the directory. I using 15.2.1559.

As a test, I created a new model and I could add the person I wanted to a Security Group on that model, so doesn't seem to be an underlying Windows AD issue (or EA ought to not accept them on any model). Neither model previously had any user security enabled.

While I can add them as a named user (i.e. not using Windows AD), it is much nicer for EA to just start and pickup the user from Windows AD rather than ask for user and password.

Has anyone else had this and identified a cure?

[Geert Bellekens]

Have you checked if the user has first and last name defined in Active Directory?

A few versions ago EA crashed when that happened. Now not anymore.

Geert

[PeteC]

I've checked now and yes they do have a first and last name defined. I wonder if there is something not defined consistently which EA is relying on?

[Modesto Vega]

Have you "imported" this user into the file? If you have, is it the first or last user in the list?

Have you run an integrity check on the problematic file?

[PeteC]

I can't import them - that is the step that is failing.

Running an integrity check makes no difference.

[Geert Bellekens]

You'll have to compare this user in Active directory to another user that doesn't pose any issues.

I'm guessing the this user will have an empty field somewhere. In the past I've seen this with first or last name, but there might be other fields that cause the same behavior.

Geert

[Modesto Vega]

If I understood Pete correctly, he cannot import them into an existing project file but he can import into them into a new project. This suggests a problem with the project file but the integrity check does not solve the problem, which is odd.

If it was an AD problem, I would expect the problem to reoccurred with a new project file.