Messages beginning with AXML are issued by the Core Driver during interactions with the Identity Manager engine.
Explanation:
The action succeeded.
Action:
No action is required.
AXML0006E The event could not be processed. The driver will retry the event.
Explanation:
The event could not be processed because an error occurred during processing. The nature of the error could be transitory, so the event is retried.
Possible Cause:
This error can be caused by configuration problems with the Core Driver.
Action:
Examine the Core Driver logs to see if errors are being generated by the event. Use the Core Driver documentation to determine the cause of the error and how to correct it. After you correct the problem, the event should succeed when the Core Driver retries the event.
AXML0008W The driver is in discard-events mode and will not process events.
Explanation:
Discard-Events mode is used when you do not want directory events to be processed by the Core Driver. This can be useful if you have a large backlog of directory events. The driver discards directory events.
Possible Cause:
The Discard Events driver parameter of the Driver object is set to true.
Action:
To return to normal mode, open the configuration parameters of the Driver driver object in iManager, and select the Driver Parameters. Change the Discard Events parameter to false.
AXML0012W Some initialization parameters could not located; default values are being used.
Explanation:
Default values for either the ASAM root directory or the Locale, or both are being used. The default directory depends on your operating system. The default locale is en for English. This could cause problems if these values are not valid for your installation.
Possible Cause:
The ASAM root directory or Locale values were left blank in the Driver object parameters.
Action:
If you do not want to use default values, open the Core Driver Driver object in iManager, click the Driver Parameters tab, and change the parameters to the desired values.
AXML0013E The event for object dn failed with error code code. The event has been discarded.
Explanation:
The event could not be processed because an error occurred in the Core Driver. This error could not be corrected, so the Core Driver has discarded the event.
Possible Cause:
This error can be caused by configuration problems with the Core Driver.
Action:
The error code usually corresponds to an LDAP error. Some more common LDAP errors and suggested actions follow.
3, 85 - Time-out. Increase the LDAP time-out value in the Web interface.
16 - No such attribute. The system attempted to access an attribute that was not present on an eDirectory object.
17 - Type not found. The schema might not have been correctly updated.
32 - Object not found. The system attempted to access an eDirectory object that was not present.
49 - Invalid credentials. Check the username and password in the Driver object parameters.
51, 52 - Busy/unavailable. Check the health of your LDAP server using DSTrace.
81 - Server down. Restart your LDAP server, or check network connectivity between the Core Driver server and the LDAP server.
For a full list of eDirectory errors, see your eDirectory documentation.
An error of -1 is an internal error. In this case, and for all errors, examine your log files for more information about the error.
AXML0014E No GUID could be found for the event.
Explanation:
The GUID attribute for the event was not present in the XML document sent by the Identity Manager engine.
Possible Cause:
The GUID attribute might not be enabled in the driver Subscriber filter.
Action:
Make sure the GUID attribute is enabled for Aliases, Users, Groups, and Organizational Roles in the driver Subscriber filter.
AXML0015E Could not retrieve the LDAP attribute map. The ASAM Master User and Password driver parameters might be invalid, or the specified user does not have sufficient rights.
Explanation:
The Core Driver attempts to load a mapping of LDAP attribute names to eDirectory attribute names. This message is issued when the driver cannot load this mapping. The driver cannot start if it cannot read the attribute map.
Possible Cause:
The LDAP Host and Port driver parameter might be invalid.
The ASAM Master User and Password driver parameters might be invalid. By default, a user named ASAMMaster is used to log in to eDirectory with an installation-generated password.
eDirectory or LDAP on the specified server might be down or in an error state.
Action:
Check the LDAP Host and Port Driver object parameters, and verify that LDAP is running on the specified host and port. If a DNS name is specified, verify that DNS is working on the Core Driver host server.
Check the ASAM Master User and Password parameters to make sure a valid user and password are specified. Also, make sure the user has sufficient rights.
Verify that eDirectory and LDAP are healthy on the specified server.