COREid services start before LDAP
In COREid deployments where the Access and/or Identity services are installed on the same box as the LDAP server, the COREid service(s) sometimes start faster than LDAP.
This behavior will cause errors in the oblogs (ie Directory is unreachable, down, or incorrect connection parameters were specified) after a reboot, and will cause the service(s) to stop (when the LDAP in question contains the COREid configuration container).
To avoid this problem on Windows platform installations, dependencies between the services can be created:
- Locate Registry Entry for LDAP Service and note name: (ie HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADAM_*)
- Locate Registry Entry for COREid Service(s): (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ObAAAServer-*, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ObOISServer-*)
- In each, add a Multi-String Value called DependOnService with a value that is the name of the LDAP service (ie ADAM_*)
After rebooting, the COREid service(s) will wait until the LDAP service has sucessfully started before starting.
This type of configuration is only useful when the COREid service(s) are configured to ONLY connect to one LDAP instance (no failover or redundancy) that is located on the same server (ie development/test environments)
Multiple LDAP service names can be added to these registry keys (if using seperate LDAP directories for user, policy, or config containers)
This dependency relationship will also cause COREid service(s) to restart/stop when restarting/stoping LDAP service