Problems with Core Driver configuration can result in improper driver operation. The messages logged by Identity Manager Fan-Out Driver components can lead you to the source of such problems.
Ensure that rights are properly set to enable the driver to perform its functions.
For the rights required by the ASAM Master User object, see ASAM Master User Security.
For the rights required by administrative users, see Rights Required for Web Application Use.
Ensure that your platform has a valid certificate. For more information, see Section IV, Platform Services Administration.
For platforms that use the DES interface, ensure that the DES encryption key specified for the platform in the Platform Configuration object and the DES encryption key specified in the platform configuration file are identical.
Ensure that the Core Drivers referred to by your platform configuration file are running and that they are using the network address and TCP port number specified in the platform configuration file.
Examine the Core Driver and Platform Services Process log files.
Ensure that your platforms have been upgraded to the current version when you upgrade the Core Driver.
Verify that LDAP is running on the servers that hold replicas of User and Group objects covered by Census Search objects.
Verify that the platform certificate has been created on the host running the Platform Receiver.
Ensure that the Core Drivers referred to by your platform configuration file are running and that they are using the network address and TCP port number specified in the platform configuration file.
Examine the logs generated by the Platform Receiver and the Core Driver for error messages.
Ensure that Census Trawls are being run at appropriate intervals and that they complete without errors.
You can check to see when daily Census Trawls are scheduled through the Web interface. For details, see Specifying Trawl Times.
You can view the Exceptions to see if any naming exceptions have occurred. For details, see Reviewing Naming Exceptions.
You can check the Core Driver Operational Log to see when the last Census Trawl was completed. Examine the Core Driver Operational Log for any potential errors that could have prevented the successful creation of Census information.
Ensure that your Census Search object parameters are set so that all intended users are included in the Census. For details, see Configuring Search Objects. You can review the contents of the Census by using the Web interface. For further details, see Displaying Provisioning Details.
Census entries relate to objects in eDirectory using their globally unique identifier (GUID). This prevents accidental reuse of a name from resulting in unintended access to resources. If a user that is represented in the Census is removed from eDirectory, the Census entry is marked inactive. If a new User object with the same name and context is created in eDirectory, the old Census entry remains inactive and a naming exception occurs.