Ldap Error 91
Contents |
License agreement Sales policy 508 statement Report piracy Shopping More ways to buy Shopping FAQ Support FAQ Online Help Request & Feedback Subscribe Forum Customers What Users Say News Links Login • Register Username: Password: | Log me
Ldapexception(resultcode=91 (connect Error)
on automatically each visit Board index ‹ Public Forums ‹ General Discussion Change font connect error result code: 91 (connect error) size Advanced search FAQ Register Login error (91) cant connect to LDAP server General Discussion about LDAP Administrator Moderator: Support Post
Ldapsearch Connect Error 91
a reply 8 posts • Page 1 of 1 error (91) cant connect to LDAP server by ottopit » Mon Dec 01, 2003 6:27 pm This is a Netware 6.0 server.I used to have ldap error 81 it working but I think when i installed iFolder on the server it hosed up my certificates or something? Anyone know error 91? ottopit Posts: 4Joined: Mon Dec 01, 2003 6:24 pm Top by Support » Mon Dec 01, 2003 6:37 pm Looks like you are attempting to connect using SSL. Using SSL connection with LDAP Browser/Administrator requires a few additional steps to be performed. Support ldap error codes Posts: 872Joined: Sun Aug 12, 2001 12:00 am Website Top by ottopit » Mon Dec 01, 2003 8:25 pm actually I had the SSL working and followed the instructions you posted but the error is 91 not 81. any ideas. It may be that I have a corrupt certiface object in netware?? ottopit Posts: 4Joined: Mon Dec 01, 2003 6:24 pm Top by Support » Wed Dec 03, 2003 12:54 pm Are you sure your server is up and running? Is there a firewall in your network? Have you tried to connect your server using an alternative tool? Support Posts: 872Joined: Sun Aug 12, 2001 12:00 am Website Top by ottopit » Wed Dec 03, 2003 9:42 pm I can connect through 389 so it appears to be up and running however the SSL seems to be the issue.I had SSL working before and got the 81 error I used netscape browser and copied the certificates after connecting to my LDAP server and had it working.It quit working after an install(iFolder) and after I try to replace the netscape certificates in the LDAP client directory I get error 91 I was hoping I may be able to solve it by finding out wha
connect to the LDAP server Next message: [OpenAM] Openam for service provider Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On 07/21/2011 09:10 AM, Charles Wang wrote: > Anyone might know of this error message below, it is openAM with openDS > as the data store > > > Plug-in com.sun.identity.idm.plugins.ldapv3.LDAPv3Repo encountered an > ldap exception. LDAP Error 91: Your LDAP client failed to connect to the > LDAP http://www.ldapadministrator.com/forum/error-91-cant-connect-to-ldap-server-t194.html server. This could have several reasons depending on your configuration of the datastore. What does 'OpenDS' datastore mean... localhost, other box, SSL ......... > > The message shows in the Privilege section of the admin console. You may set debug level to message (for logger IdRepo or in general , f.e. using 'Debug.jsp') and look into https://lists.forgerock.org/pipermail/openam/2011-July/022818.html 'IdRepo' debug log. > > We are new to openam/ds, any hints? I'm afraid a community alias can not save you from getting some training / lecture first if the basics are missing ... -Bernhard Thanks. > > -- > Best, > Charles > > > > _______________________________________________ > OpenAM mailing list > OpenAM at forgerock.org > https://lists.forgerock.org/mailman/listinfo/openam -- Painstaking Minds IT-Consulting Bernhard Thalmayr Herxheimer Str. 5, 83620 Vagen (Munich area), Germany Tel: +49 (0)8062 7769174 Mobile: +49 (0)176 55060699 bernhard.thalmayr at painstakingminds.com - Solution Architect This e-mail may contain confidential and/or privileged information.If you are not the intended recipient (or have received this email in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Previous message: [OpenAM] LDAP Error 91: Your LDAP client failed to connect to the LDAP server Next message: [OpenAM] Openam for service provider Messages sorted by: [ date ] [ thread ] [ sub
Server-Side Result Codes Various LDAP specifications define a number of common result codes that may be included in responses to clients. These result codes include (but are not necessarily https://www.ldap.com/ldap-result-code-reference limited to): 0: Success This indicates that the operation completed successfully. It may be http://forums.mozillazine.org/viewtopic.php?t=74809 returned in response to an add, bind, delete, extended, modify, modify DN, or search operations. Compare operations will not return a success result. If a compare operation does not encounter an error during processing, then the server should return a result of either "compare true" or "compare false", based on whether the target entry ldap error had the specified attribute value. 1: Operations Error This is intended to indicate that the client has requested an operation at an inappropriate time or in an incorrect order. For example, it may be used if a client sends a non-bind request in the middle of a multi-stage bind operation. Note that some directory servers use this as a generic "server error" type result. This is not the 91 (connect error) intended use for this result code (the "other" result is a better choice for this), but clients may need to be aware of this possibility. 2: Protocol Error This generally indicates that the client request was improperly formatted in some way. For a bind operation, it may indicate that the client attempted to use an unsupported LDAP protocol version. For an extended operation, it may indicate that the server does not support the extended request type. Note that this result code can only be used if the server is able to at least partially decode the request in order to determine the message ID and operation type, since the server needs that information in order to craft an appropriate response. 3: Time Limit Exceeded This indicates that a search operation took longer to complete than allowed by the maximum time limit for that operation. This may be the time limit specified by the client in the search request, or it may be a time limit imposed by the server. 4: Size Limit Exceeded This indicates that a search operation would have returned more entries than were allowed for that operation. This may be the size limit specified by the client in the s
Posts: 1Joined: May 6th, 2004, 4:59 pm Posted May 6th, 2004, 5:05 pm Have entered all the correct information (Hostname & Port Number) for the LDAP server but get the error code when entering addresses into the To: field. Saw the Known Issues report about LDAP v2 vs v3 but I am not getting the "initialization failed, error code 2: protocol error" message. Any thoughts 1 post • Page 1 of 1 Return to Thunderbird Support Jump to: Select a forum ------------------ Mozilla Firefox Firefox Support Firefox General Firefox Builds Firefox Features Firefox Bugs Mozilla Thunderbird Thunderbird Support Thunderbird General Thunderbird Builds Thunderbird Features Thunderbird Bugs SeaMonkey/Mozilla Suite SeaMonkey Support SeaMonkey General SeaMonkey Builds SeaMonkey Features SeaMonkey Bugs Other Mozilla Discussion Camino Calendar Mobile Miscellaneous Support Other Applications and Distributions Extensions and Themes Extension/Theme Releases Extension Development Theme Development Development Mozilla Development Web Development / Standards Evangelism Third Party/Unofficial Builds MozillaZine MozillaZine Site Discussion MozillaZine Tech Post a reply Who is online Users browsing this forum: Google [Bot] and 4 guests Board index ‹ Mozilla Thunderbird ‹ Thunderbird Support All times are UTC - 8 hours [ DST ] Login FAQ / Rules Register Search Boards : Knowledge Base: knowledge base chat about fr ja es mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same. Proudly Powered by phpBB © phpBB Group © 1998-2015 mozillaZine All Rights Reserved