ERROR:Unknown//Exception has been thrown by the target of an invocation

I had this problem on a fairly straight forward migration. The data migration tool seemed to load all entities are loaded without problems.
However, during the migration of the activity entity I receive the error following error:

"ERROR:Unknown//Exception has been thrown by the target of an invocation"

You receive this error prior to importing any records for the Activity Object. Checking all entries in the Activity table doesn't show any irregularities in the formating or data.

Below is an output from the Log file.

-----
". Migration phase completed

Processing entity: Activity
Entering Correlate
Starting migration phase
ERROR:Unknown//Exception
has been thrown by the target of
an invocation.

Processing entity:
SystemUser
Starting update phase
Update phase completed

Processing entity: Account
Starting update phase
.................................................. Update phase
completed

Processing entity: Contact
Starting update phase
Update phase completed"

After looking into the processing of the Stored Procs I discovered that the error is due to the Migration tool trying to create a table 'cdf_ActivityPartyTemp'. The migration may have failed (or been stopped during processing) that has resulted in a temp table being left behind.

Remove this table and run the migration process. With the table removed it will allow the 'p_dm_GetActivityParty' to execute and will stop this error from occuring.

There may be other causes for this issue but in my case the 'cdf_ActivityPartyTemp' was the issue.

Problems with Security Roles

When you create a new role in Microsoft Business Solutions CRM 1.2.
On the Role: New Web page, you click the lookup button next to Business Unit. You type a filter in the Find box. You expect that only the business units that match that filter will appear under Available Records. Instead, all business units appear.
By default, the lookup list next to Business Unit lists the first 100 business units. This feature cannot filter the business units by the first letter, or letters, of the business unit name.

Work Around: Because of other problems with Microsoft CRM Security roles, we do not recommend that you create, copy, or make privilege changes to Microsoft CRM roles at the child business unit level. Instead, create new roles and change existing roles at the root level. Any roles that you create, copy, or change at the root level are propagated to every child business unit. These roles will be available to assign to Microsoft CRM users.