During migration session the following error is written to the DSA.log file "Error in attribute c (4261959)

During a directory migration session the following error is logged in the DSA.log file.

1/23/2009 11:42:02 AM (GMT-04:00)     Target JobID:0 -> object was not created due to error
1/23/2009 11:42:02 AM (GMT-04:00)     Common JobID:0 -> Error 0xe1000040. Per attribute apply failed for object cn=joe,OU=Source Migrated Objects,DC=target,DC=com
Error 0xe1000041. Apply of attribute samaccountname2 with value(s) = joe2 failed.
LDAP error 0x10. No Such Attribute (00000057: LdapErr: DSID-0C090B73, comment: Error in attribute conversion operation, data 0, v1771).
1/23/2009 11:42:02 AM (GMT-04:00)     Target JobID:0 ->  Handlers Manager started the point: FAILED_CREATION

The attribute mentioned in the failure may differ, however the result is the same.  In this case the attribute was samaccountname2.

This error is the direct result of an incorrectly formatted import file.  Specifically the header in this case had "samaccountname2" as an attribute.

This causes the DSA to attempt to write a non-existant attribute to the target domain.  The result is that the account is created with the orignal source attribute, however the mapping is not placed within the ADAM database.

This will cause problems with any .ini file creation for processing by any of the agents.

Correct the incorrectly formatted import file, and simply re-migrate the objects again.

From CASEID:688394.  This has been logged as a bug for QMM ST-57548.  The migration session should fail.