HTTP 500 on replication tasks

[phillxnet (Philip Guyton)]

@sebasb Hello again.

From the provided log except this looks to be the known failure referenced last we spoke:

@phillxnet

Remember we still have a fragility in the replication system re existing snapshots from prior failed replication tasks. It will indicate this as a failure if you are affected. Just delete the ‘blocking’ snapshot if you are affected by this and kick off another.

ie the:

@sebasb

Snapshot (Profiles_19_replication_290) already exists for the share (Profiles)

Bit.

Not very helpful I know, but that’s all I see in this bit of log.