OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
June 5, 2017
OpenDJLDAPldapsearchForgeRock

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!'


Remember, bat for windows!

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

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.

https://technicalconfessions.com/images/postimages/postimages/_443_5_Result Code 91 connector error.png

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

https://technicalconfessions.com/images/postimages/postimages/_443_9_logging in using openDJ control panel.png

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...
E_WARNING Error in file posts.php at line 464: fopen(http://www.technicalconfessions.com/images/postimages/postIcons/pp444.png): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error

TomcatJava-8PKICAS

June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...

IDM ERROR - JDBC repository configured but datasource default was not found

ForgeRockIDMJDBC

May 23, 2017
Created by: Daniel Redfern
IDM ERROR - JDBC repository configured but datasource default was not found
Read More...

OpenIDM Issue - javax.crypto.BadPaddingException: Given final block not properly padded

OpenIDMIDMForgeRockcryptography

May 23, 2017
Created by: Daniel Redfern
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded
Read More...