This is for an old version of OpenDJ (2.6 to be exact) though that shouldn't matter. Fairly explicit error however it became more of a factor trying to troubleshooting an it needed. It also justified me writing a blog about it knowing that future Daniel comes back and say, 'oh, thanks Past-Daniel!'

Firstly, the ldapsearch.bat is the file that needs to be executed. This can be located within the opendj\bat. A lot of the ForgeRock supports the UNIX commands (which I also prefer) though the bin directory here is redundant.

It's the ldapsearch.bat file and not the ldapsearch file that is needed here. In hindsight, it's obvious. I do feel idiotic writing this though when you're more a unix-than-a-windows-guy (which is a real thing!) and when you're following the ForgeRock documentation, it's not completely obvious. When you execute the .\ldapsearch command though it prompts you with a 'How do you want to open this file?', the first thing that came into mind was an ACL permissions issues

Back to the error, "Connect Error Result Code: 91 (Connect Error)". The LDAP command can be executed using the .bat file though this constantly popped up. This non-ssl connection should always be executed on the LDAP instance itself for obvious reason. Also, this is why you would see examples as having the parameter as -h localhost. This is OK though explicitly indicating the FQN or IP address could resolve this for you.

The next parameter is the username and password. The openDJ control panel can be started and you can use the username/password in there. Again, this is located within the bat directory.

Confirming the username/password would eliminate the possibility that it's a credential issues. Then, them there's the port number. Turned out that this was the issue for me. When reviewing the opendj/logs/server.out file, the following was logged.

category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444. category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 389. category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully

... This say the classic 389 port number for LDAP. Why was I using 1389. Turned out that the example queries I intended to use indicated a different port number. Again, simple enough though took time to discover such an issue as well as write this blog! Comments below are always welcome

About the author