The screenshot submitted seems to cut off the entire error message, including the specific LDAP error code you may be receiving.
Looking at the rest of the error message the issue appears to be due to a bind outstanding.
A common cause of this error is if your AD server doesn't have enough open connections to server the request before it times out.
A good place to start would be to have your AD admin investigate if there needs to be an increase in the bind pool connections on AD.
You'll also want to verify the AD configuration in Jira is correct and that there are no network problems between Jira and AD such as high latency.
Beyond this we would need to look at your atlassian-jira.log after reproducing the error, and have your AD admin look at the AD logs after reproducing the problem to see what other information can be gained.
sorry, full error message is:
Test retrieve user : Failed
org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.ServiceUnavailableException: [LDAP: error code 51 - 00002024: LdapErr: DSID-0C060598, comment: No other operations may be performed on the connection while a bind is outstanding., data 0, v1db1]; remaining name '']For more information regarding LDAP error codes see Troubleshooting LDAP Error Codes.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs