It seems that this issue is reproducible only with Sql Server 2012 and originates only when conflicts are present during the synchronization.
Any successive synchronizations, even with new replica registered on this geodatabase, seem to encounter the "Table already Exists" error.
The issue does not seem reproducible with other versions of Sql Server (for e.g. Sql Server 2008 R2.)
just got off phone with with ESRI and no luck so far.
For what its worth, when I run the synch tool from toolbox instead of the wizard tool bar i get the 'table already exists' in the results messages but also get a 'error 000582'.........which unfortunately is a catch-all type of error.
Mandar, is there a bug reported? Because if not right now i'm not seeing any resolution or work around and if I understand what you're saying correctly if you have conflicts and if you have a 2012 DB server...you're outta luck? I'd suspect that there are a lot of people with this deployment scenario.
I have seven deployments in which two are using replication. If this is a 2012 DB server issue, this needs to be fixed ASAP. All my new deployments are built on sql server 2012. It doesn't make sense to deploy on older versions.