The most common cause of this error, in my experience, is that someone has failed to mark a trigger "not for replication" that needed to be so marked. The correct long term solution is to fix the trigger, and then reinitialise and restart the subscription.
Doing all four things recommended here serious risks leading to catastrophic error - two of them just say "I don't care if it's wrong, just get on with it", which is normally considered completely unacceptable (it's as bad as running all your queries with hordes of NOLOCK hints). If someone is updating a subscriber which is not handing stuff back to the publisher, that probably needs serious management action to ensure that it doesn't happen again, not just deleting a row on the subscriber. So three of the four things are just plain wrong.