Previous Topic: Automated Administration of Secondary Authids

Next Topic: TSO Alias Support

Errors

If an error occurs on an add or modify Account transaction related to Secondary Authids, the LDAP server will return an error code of PARTIAL_SUCCESS. This tells CA Identity Manager that an error occurred during processing, but processing continued and the transaction is to be considered a success. The reason for this is that any processing that had already occurred against the Account (creation, modification, and deletion) will have occurred successfully before Secondary Authid maintenance was performed. The Provisioning Manager will report the error, but proceed as a successful transaction. The error can then be reviewed, and appropriate action can be determined and taken against Secondary Authids.

For Account delete transactions, if an error occurs during Secondary Authid maintenance, this error will be returned as an error and the Account will not be deleted. This is because the eTA LDAP Server does not handle partial success situations with Account deletes; therefore the message returned must be a success or failure. Review the error returned and take appropriate action to enable the transaction to proceed properly.

The following error messages can be returned when an error occurs with Secondary Authids:

LDP0143E Manual maintenance required for XREF SGP record(s): recordlist,…

An error occurred during maintenance of at least one Secondary Authid record and the user will need to examine this list of records and provide appropriate maintenance based upon the type of transaction that occurred.

LDP0144E F ACF2,NEWXREF failed and manual maintenance required for XREF SGP record(s): recordlist,…

This is similar to the message above, but the refresh command failed also. Take appropriate action against the list of Secondary Authids and issue a F ACF2,NEWXREF command when completed.

LDP0145E F ACF2,NEWXREF failed.

The F ACF2,NEWXREF command failed and needs to be issued manually.