PK violation error during replication

While replicating some tables into another sql server for
DB sync., I run into a problem as follows;
========================================
===================
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
Violation of PRIMARY KEY
constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
duplicate key in object '#65EA00FF'.
(Source: TUBE\TUBE2 (Data source); Error number: 2627)
========================================
===================
At MSDN, I found it's a kind of sql server bug.
(See, http://support.microsoft.com/default.aspx?scid=kb;en-
us;813494)
Unfortunately, to solve it, contact to Microsoft was
required and it cost some money & time to get the hot fix
from MS headquarter.-Currently, I'm in Asia.
So, I'd like to ask you guys to e-mail
(lovelydovey@.msn.com) me the hot fix, if you have. Or, if
there's another way to solve this problem, pls, tell me
the rope..!
e-mail : lovelydovey@.msn.com
Your answer would be appreciated!Do the service pack... Even if it is some trouble.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Park" <anonymous@.discussions.microsoft.com> wrote in message
news:268e101c4634e$4f0ff020$a601280a@.phx
.gbl...
> While replicating some tables into another sql server for
> DB sync., I run into a problem as follows;
>
> ========================================
===================
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> Violation of PRIMARY KEY
> constraint 'PK__@.snapshot_seqnos__66DE2538'. Cannot insert
> duplicate key in object '#65EA00FF'.
> (Source: TUBE\TUBE2 (Data source); Error number: 2627)
> ========================================
===================
>
> At MSDN, I found it's a kind of sql server bug.
> (See, http://support.microsoft.com/default.aspx?scid=kb;en-
> us;813494)
> Unfortunately, to solve it, contact to Microsoft was
> required and it cost some money & time to get the hot fix
> from MS headquarter.-Currently, I'm in Asia.
> So, I'd like to ask you guys to e-mail
> (lovelydovey@.msn.com) me the hot fix, if you have. Or, if
> there's another way to solve this problem, pls, tell me
> the rope..!
> e-mail : lovelydovey@.msn.com
> Your answer would be appreciated!
>