Re: Receiving 'PRIMARY KEY constraint 'PK__@snapshot_seqnos' error...
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Sun, 16 Oct 2005 12:46:55 -0400
Have a look at this post.
http://groups.google.com/group/microsoft.public.sqlserver.replication/msg/7a54ed86febfd7b0?dmode=source
This will fix it. IIRC you will make this change on the distributor.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"DTully" <DTully@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:45B780CE-96CF-45AE-8716-BE22A062C5FE@xxxxxxxxxxxxxxxx
> I'm adding a new subscriber to a transactional publication (no snapshot)
> and
> I'm receiving a 'Violation of PRIMARY KEY constraint
> 'PK__@snapshot_seqnos__543BF21A'. Cannot insert duplicate key in object
> '#5253A9A8'.' error. The subscriber, remote distributor and publisher are
> all
> running SP3.
>
> I did some research and it appears this is fixed in MS03-031:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;813494
>
> Can this be installed just on the distributor w/o affecting the other
> systems? We actually have 5 other subscribers and some also publish to
> other
> subscribers and also to other publishers so I don't want to affect any of
> the
> other other servers.
>
> TIA!!
> Darin
.
- Prev by Date: Re: ABNORMAL Transactional Replication behaviour
- Next by Date: Re: Replicating Multiple Databases
- Previous by thread: Re: Receiving 'PRIMARY KEY constraint 'PK__@snapshot_seqnos' error...
- Next by thread: Re: Consolidate multiple databases via merge replication
- Index(es):
Relevant Pages
|