It depends on the application, but in many SQL Remote setups the response to broken synchronization is to start over with the remote database: Throw away the existing remote database, and run the extract process on the consolidated database to recreate it.
That won't work if the remote database contains critical data that does not participate in synchronization and/or will not be recreated on the remote by the extract process.
But if the remote database is entirely a subset of data on the consolidated database, re-extract is the generally the way to go... trying to repair a broken sync setup is fraught with error.
