You are viewing limited content. For full access, please sign in.

Question

Question

LF 11 Admin Console Error: "LDAP query could not be completed. [9357]" when querying LFDS Users/Groups

asked on March 6, 2023

Hello,

I created a new group in LFDS that I am trying to add in the LF Admin Console->Laserfiche Directory Section, but I am getting the following error:

LF Admin, LF Server and LFDS are all on the same machine and all are version 11.

Appreciate any feedback anyone might have on this.

Jeff Curtis

0 0

Replies

replied on March 6, 2023

What version of Laserfiche Server are you using? From the List of Changes for Laserfiche Server 10.2.1 Update 3

  • In certain situations, you may receive a "LDAP query could not be completed. [9357]" error message when attempting to retrieve user information from Laserfiche Directory Server. This issue is now resolved. (37476)
  • You can now properly register Directory Server users and Windows accounts in the Laserfiche Administration Console. (45905)

 

Might be a good idea to update if you haven't already.

replied on March 6, 2023

Hey Kevin,

I am using Version 11

As an FYI- 10.2.1 is not even supported by LF anymore, so if you are on an LF version older then 10.3.1, you should update your software to 10.4 or 11 for all of the core server components.

Jeff

replied on March 7, 2023

Do you get the error for any LFDS User/Group, or only this new LFDS Group?

If only the new group, try deleting it in LFDS, recreating it, and then re-adding it in LF Admin Console.

You should also try adding it through Web Client -> Administration to see if you get the same error there.

0 0
replied on May 30, 2024

Just to update this, this is when searching for any LFDS group in the LF admin console, adding it through the web client goes through the motions, you click ok, but then the group is never added to the list.

 

It's identical to this post https://answers.laserfiche.com/questions/215118/Adding-LFDS-GroupUser-to-Repository--Error-9357

0 0
replied on January 24, 2024

Was there an update on how this was resolved?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.