If the Identity Manager drivers for cluster synchronization do not start, the problem might be caused by one of the following conditions:
A certificate has not been created. For information, see Creating SSL Certificates.
The ports used by the driver are not unique and available.
Each eDirectory driver must listen on a different port number. To specify the port number, access the driver properties in iManager and specify the appropriate port number in the IP address field. See Section 2.4.1, Configuring Identity Manager Drivers for the Business Continuity Cluster for more information.
The format for specifying the port number in the IP address field is remote IP:remote port:local port. For example, you could specify something similar to 10.1.1.1:2001:2001. If it is not being used for other drivers, port 2001 can be used for the User object driver and port 2002 for the Cluster object driver.
The driver has been disabled.
Click the red icon for the driver on the DirXML Driver Overview page. You can enable the driver by using the radio buttons in the Driver Startup section of the page that displays.
Selecting the Auto Start option is recommended.
Unknown communications problems.
-670 errors in the DSTrace logs. See TID # 10090395
This is commonly caused by rconag6.nlm loading before SAS, which causes problems when Identity Manager tries to load. The load order is sometimes changed by the installation of a product that changes the order of the lines within the autoexec.ncf file.