Single transaction in mysqldump seems to break replication (1 reply)

We have a database where there is one table that has to be MyISAM for it's Full Text Search Key

The mysqldump syntax used to create the dumpfile is: mysqldump --all-databases --master-data=2 --single-transaction | gzip > dump_file.sql.gz

The dump is imported on the target server Fine.
The change master to master_host, etc. is run and start slave is fine.
Soon thereafter the Slave error 1062 pops up with
Last_Error: Error 'Duplicate entry 'xxxx' for key 'PRIMARY'' on query. Default database: 'yyyy'
The query involved is an insert into the same innodb table each time.

The data that it states that is duplicate is not the primary key.
It is actually the fourth column which is char(36) defined in the table and does not have any indexes or keys. It is a unique generated value by the code.

The PK is

PRIMARY KEY (`id1`,`id2`) where id1 is a char(36) and id2 is an int

There isn't a tie into the FTS table with any FK
The do have id1 in common for column name and datatype.

I dumped from master. I dumped from slave. Same issue.

If I remove --single-transaction from the mix the process works fine and the new slave has no issues with replication.

Any ideas why this could occur?