Jeff
Thanks for you response, the version that we use in production is 10.0.1.3835, I know is an old version but still the issue should not be happening.we have conducted and extensive troubleshooting and the transaction that fails it correctly replicated to this remote database, the issue as to why is is failing is a different story, but the transaction that gets rolled-back along with the legitimate failed transaction should not fail. in fact if we translate the db log and get the db transaction we apply it manually it does not give an error, that what we are ending up doing in order to resolve the missing data issue.
I am attaching a SQL file (translated from the replication session) that isolates the roll back you will see that there are 3 logical unit of works but only one roll back, only the first transaction should have been rolled back.
I will test the -g 1 option to see if it enforces the commits the way the are done by the application that originally posted the transaction.