problem 22 (Invalid argument) when using Quest AD Migration Manager

Environment: Migrating users from Windows 2003 R2 SP2 Standard Edition to Windows 2008 R2 Standard Edition Domain. They are independent domains with an established 2-way transitive trust.

We are in the process of testing out Quest Tools for AD Migration.

1. As stated above, a 2-way transitive trust was established between our source and target domains. Source domain is Win2k3 and target is Win2k8. All servers in each domain have the same version of Windows running across the domain, so Win2k3 Domain has all Win2k3 servers.
2. We setup our Quest Server with the Tools installed and joined it to the target domain.
3. WINS is setup within the subnet we are testing in and it is registering all of the client systems we are working with along with all servers from both domains.

Below is the question:

After feeding Quest Tools our csv file and running the migration wizard for 2 user accounts we receive the below error. We are choosing to merge accounts based on sAMAccountName matching rule. Why are we getting the below error?

Data below has been edited to use generic values, but syntax is just like the log file view generated by the migration wizard.

Failed Object 1:

CN=User 1,OU=Users,OU=Migration_Test,DC=subdomain,DC=main,DC=domain

Object Class:

user

Error:

LDAP error 0x50. Other (00000523: SysErr: DSID-031A1202, problem 22 (Invalid argument), data 0
).

In addition, below is the format for our csv file using tabs as delimiters:

SAMAccountname SAMAccountname Name

dduck 991212123 DonaldDuck
mmouse 991212124 MickeyMouse

(2nd SamAccountName is a 9-digit ID we made up, since our target domain uses a 9-digit ID as the value for the SamAccountName attribute)

In the migration wizard we choose the following options for the various steps in the below order:

1. Step 1: Source Objects: The two user objects provided above.
2. Step 2: Select Target Container: We selected the OU we designated as our ADMigrationTest.
3. Step 2: OU Hierarchy under step 2: We chose, "Migrate objects without OUs as a flat list."
4. Step 2: When merging with existing accounts on target under step 2: We chose, "Merge and leave the account where it was before the migration.
5. Step 3: Security Options - Skip Security Description migration rule.
6. Step 3: Group Options - Add source members to the corresponding target groups.
7. Step 3: User Principal Name handling - Copy
8. Step 3: Password options - Password handling - Skip account password.
9. Step 4: Object Processing Options: General - Enable target accounts.

Sorry for the long post, but I wanted to make sure that someone had all most of what they need, so that you could quickly answer my question and there is little to no back and forth.

FYI: We have contacted Dell and they said, they DO NOT recommend using the sAMAccountName to match on. We also did Google searches and nothing seems to help us.

I am hoping someone with practical experience can help out.

Any help is greatly appreciated, thank you!