eDirectory Issues on OES 1.0 Known Issues 1.1 Tree Name Lookup Failure 1.2 Restarting Ndsd Might Dump Core 1.3 Ldap Bind Might Fail with an Error 1.4 Timing Issues of OES on Xen 1.5 Adding eDirectory Server by Using Container Admin Prompts Errors 1.6 Unable to Bind with the Simple Password 1.0 Known Issues - 1.1 Tree Name Lookup Failure - 1.2 Restarting Ndsd Might Dump Core - 1.3 Ldap Bind Might Fail with an Error - 1.4 Timing Issues of OES on Xen - 1.5 Adding eDirectory Server by Using Container Admin Prompts Errors - 1.6 Unable to Bind with the Simple Password 1.1 Tree Name Lookup Failure While adding 64-bit SLES 10 SP1 as a secondary server, the following errors appear on the screen: Tree names do not match. Joining a tree with old version of eDirectory. You can ignore these messages and continue the eDirectory configuration. 1.2 Restarting Ndsd Might Dump Core The core dump happens randomly. It may not be a frequent occurance. 1.3 Ldap Bind Might Fail with an Error LDAP bind operation fails randomly with the following error message: LDAP_SERVER_DOWN This error does not occur if you restart or refresh the server. 1.4 Timing Issues of OES on Xen Connection with eDirectory on guest operating system (SLES 10) is lost if the system time varies in the host operating system. To work around this issue, do the following: 1. Shut down the guest operating system. 2. Type echo 1 > /proc/sys/xen/independent_wallclock in host operating system CLI. 3. Restart the operating system. 1.5 Adding eDirectory Server by Using Container Admin Prompts Errors The error message appears because the user does not have the necessary rights to create the objects. 1.6 Unable to Bind with the Simple Password After uploading an object using the ICE command ice with -l switch, you fail to log in to with that objects' credentials. This is because of simple password that uses NMAS method fails.