DS52 Patch 4 & 6 - Authentication as cn=Directory Manager Failing with Err=49 During Installation, New Instance Creation or Normal Bind Activity
(Doc ID 1310588.1)
Last updated on FEBRUARY 06, 2019
Applies to:Oracle Directory Server Enterprise Edition - Version 5.2 to 5.2 SP6 [Release 5.0]
Information in this document applies to any platform.
Symptoms can be seen while performing any of the following tasks.
- Full Installation.
- New Instance Creation.
- Normal Bind Activity.
Full Installation or New Instance Creation:
Install or Instance Creation of Directory Server 2005Q4 fails in a Solaris 10 container (whole root) using the version Directory Server 5.2 Patch 4 or Patch 6.
The directory server installation or instance creation failed with the following error message:
Your new directory server has been started.
error: can't bind to server:Unable to bind to server. (Invalid credentials (49)
returned from ldap_simple_bind_s(cn=Directory Manager))
Could not configure server.
Configuration of the Directory Server failed.
Error Directory Server configuration failure
Error Configuration of the server(s) failed.
Normal Bind Activity:
The user cannot connect to the Directory Server using cn=Directory Manager when authentications show err=49 (invalid credentials) in the access log when they previously worked with no issue.
[26/Mar/2012:14:33:54 +0200] conn=0 op=0 msgId=1 - RESULT err=49 tag=97 nentries=0 etime=0
The release of the 3.12 NSS changes a behavior common to the way that the directory server (and a number of other products) handled invoking cryptographic library for use by itself and child processes.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!