Merge Replication Primary Table Key Error

Question

We have a SQL Server 2008 database that is replicated to Australia.  The primary data tables are merge replicated.  The replication cycle is 1 hour.  We have a situation where a user inserted a row into a table, deleted the row, then reinserted
it within an hour.  The merge replication failed because of a primary key uniqueness violation on that table.  We have been told that merge replication cannot handle this scenario.  
From what little I can get from the MS literature, the replication triggers should have handled this.  The delete trigger should have removed the insert entry from the replication tables and the second insert should have removed the entry from the delete
replication tables, leaving the replication processing to only do the second insert.  Can anyone clarify what is really supposed to happen here or if this is in fact a limitation of merge replication?

Answer 1

The table creation SQL is:
CREATE TABLE [dbo].[GC_SEAM_SPEC](
      [USER_ID] [varchar](50) NOT NULL,
      [SEAM_SPEC_ID] [varchar](50) NOT NULL,
      [DESCR] [varchar](255) NULL,
      [COMPOSITE_YN] [bit] NULL,
      [CORR_SEAM_ONLY_YN] [bit] NULL,
      [INCLUDE_COAL_YN] [bit] NULL,
      [INCLUDE_COAL] [float] NULL,
      [INCLUDE_PARTING_YN] [bit] NULL,
      [INCLUDE_PARTING] [float] NULL,
      [FUZZ_FACTOR_YN] [bit] NULL,
      [FUZZ_FACTOR] [float] NULL,
      [FROTH_ANALYSIS_YN] [bit] NULL,
      [CONTAMINATION_TY] [smallint] NULL,
      [CONTAMINATION_OPTION] [smallint] NULL,
      [REPORT_OPTION_TY] [smallint] NULL,
      [AVERAGING_METHOD_TY] [smallint] NULL,
      [INCLUDE_TOP_BOT_CD] [smallint] NULL,
      [DATE_INSERTED] [datetime] NULL,
      [INSERTED_BY] [varchar](50) NULL,
      [DATE_UPDATED] [datetime] NULL,
      [UPDATED_BY] [varchar](50) NULL,
      [rowguid] [uniqueidentifier] ROWGUIDCOL  NOT NULL,
CONSTRAINT [PK_GC_SEAM_SPEC] PRIMARY KEY CLUSTERED
      [USER_ID] ASC,
      [SEAM_SPEC_ID] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]
ALTER TABLE [dbo].[GC_SEAM_SPEC] ADD  CONSTRAINT [DF_GC_SEAM_SPEC_DATE_INSERTED]  DEFAULT (getutcdate()) FOR [DATE_INSERTED]
ALTER TABLE [dbo].[GC_SEAM_SPEC] ADD  CONSTRAINT [DF_GC_SEAM_SPEC_INSERTED_BY]  DEFAULT (suser_sname()) FOR [INSERTED_BY]
ALTER TABLE [dbo].[GC_SEAM_SPEC] ADD  DEFAULT (newsequentialid()) FOR [rowguid]
There are no precomputed partitions.  Triggers on the table are the replication triggers and some audit triggers.
Thanks,
Alan