ReportServer Forum

ReportEnabler

Member

Registered: 2022-11-15

Admin login error after scheduled ldapimport

RS4.3.0-6079

When trying to login as Admin we get:

Error
query did not return a unique result: 2

Exception details start with...
javax.persistence.NonUniqueResultException: query did not return a unique result: 2
at org.hibernate.internal.ExceptionConverterImpl.convert(ExceptionConverterImpl.java:128)

So now we can't login at all.

Two days previously we had just achieved ldapimport of a flat list of 650 users, and scheduled nightly ldapimport script to run.

Anybody know how we can proceed?
thank you

ReportEnabler

Member

Registered: 2022-11-15

Re: Admin login error after scheduled ldapimport

We could not resolve this problem, so completely rebuilt the server

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Admin login error after scheduled ldapimport

Hi ReportEnabler,

you could have used net.datenwerke.rs.authenticator.service.pam.EveryoneIsRootPAM or/and a root user to delete the duplicate user. Be careful in the future: in your LDAP you should not have users with same usernames, as you will get this error again if you import them into ReportServer.

Regards,
Eduardo

ReportEnabler

Member

Registered: 2022-11-15

Re: Admin login error after scheduled ldapimport

Hi Eduardo
Yes we tried EveryoneIsRootPAM but it didn't work...(see other message) because we apparently had a second reportserver.properties file that was taking precendence.

Does the ldapimport use the object GUID to ensure uniqueness of users? or just usernames?

thanks

eduardo

Administrator

Registered: 2016-11-01

Website

Re: Admin login error after scheduled ldapimport

Hi ReportEnabler,

while importing, it compares the GUIDs in order to find/identify the object in ReportServer.

While logging in, ReportServer checks for username duplicates, and does not allow the login if more than 1 user has the same username.

Regards,
Eduardo

ReportEnabler

Member

Registered: 2022-11-15

Re: Admin login error after scheduled ldapimport

We had the default report server user, called 'admin'.
Apparently, we also had a user called 'admin' in AD.
After we imported from AD there was a confusion in report server and we could no longer login.
As mentioned above we 'solved' this by complete re-installation,
Next time we changed the report server administration user name ;-)