Do you have a numeric UDEF field in contact2? If so, you are running into a known issue with GM7.
PROBLEM
When an application (such as Inaport) creates a C2 record using the API, GoldMine issues an insert on the database, which succeeds. It then accumulates all the field values, and issues a single update to the record when the changes are commited by the application. For reasons best known to the developers, the WHERE clause to the UPDATE checks that each field being updated is currently null.
Problem with this is that with GM7, the schema definition for UDEF numeric fields was changed to have them default to 0. That means any numeric fields are set to 0 when the record is first inserted, which in turn means that the where clause fails.
WORKAROUND
In Inaport, you can work around this problem by having two instances of the _contact2 table in your table map.
On the first instance, set the operation to "Create not exist", and accept the default primary key/foreign key settings.
Change the action for "If there are multiple matches" to be: "Continue processing this source row"
Do not specify any match criteria.
Do NOT map any values to the fields - have an empty "Map for Create" grid
On the second instance, set the operation to "Update single existing"
Do not specify any match crieria
Now map all your fields to the required fields in C2
----------
In the medium term, we are working on having Inaport handle this silently for you, but at the moment this is the only work around.