Is This Content Helpful?
We're glad to know this article was helpful.
When using geodatabase replication with SQL Server 2012, two issues may be encountered:
• When synchronizing a two-way replica, duplicate Global IDs are generated when conflicts are present.
• Importing changes to a replica fails with a 'dbms table not found' error.
These issues are specific to SQL Server 2012 and are related to changes in the way local temporary tables are handled.
There is no workaround for these issues. A fix is available in the ArcGIS 10.1 SP1 for (Desktop, Engine, Server) SQL Server 2012 Support Patch.