replication conflict when use BEGIN TRANSACTION COMMIT TRANSACTION

Ok let me explain my problem
I update table abc to SERVER A
SERVER A push a replication to SERVER B
and SERVER B push to SERVER A and SERVER C
SERVER A and C are configure to replicate to SERVER B and
SERVER B is configure to replicate to SERVER A and SERVER C
(same tables are replicate)
I have no problem while I not use BEGIN TRANSACTION UPDATE... COMMIT
TRANSACTION
When I use BEGIN TRANSACTION UPDATE... COMMIT TRANSACTION I got a conflict
error
supp info:
2 Queued update conflict. Subscriber wins. Updating Publisher ...
"rl" <rlavoie@.lgs.com> wrote in message
news:%23jnEqEGjFHA.1232@.TK2MSFTNGP15.phx.gbl...
> Ok let me explain my problem
> I update table abc to SERVER A
> SERVER A push a replication to SERVER B
> and SERVER B push to SERVER A and SERVER C
> SERVER A and C are configure to replicate to SERVER B and
> SERVER B is configure to replicate to SERVER A and SERVER C
> (same tables are replicate)
> I have no problem while I not use BEGIN TRANSACTION UPDATE... COMMIT
> TRANSACTION
> When I use BEGIN TRANSACTION UPDATE... COMMIT TRANSACTION I got a conflict
> error
>

Replication Clean Up of Failed Server

On my distribution server, I have a failed replication (the big red X) for a
server that had hardware failure a couple of weeks ago. We were able to
bring this client up on a separate server and have re-replicated them. Now
I need to get rid of the failed replication however when I try to simply
delete it, it obviously cannot connect to the failed server since it doesn't
exist and therefore will not delete the information from the DISTRIBUTOR.
I would like to avoid manual system table clean up unless someone has the
method that will completely remove this information.
Is there a way to do this correctly?
Thanks,
Adam P. Cassidy
Did you follow these instructions?
http://support.microsoft.com/kb/324401
Also on your distributor you may have to issue a call to
sp_dropdistpublisher
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
"Adam Patrick Cassidy" <apcassidy@.aol.com> wrote in message
news:OnM$cTvaHHA.2436@.TK2MSFTNGP06.phx.gbl...
> On my distribution server, I have a failed replication (the big red X) for
> a
> server that had hardware failure a couple of weeks ago. We were able to
> bring this client up on a separate server and have re-replicated them.
> Now
> I need to get rid of the failed replication however when I try to simply
> delete it, it obviously cannot connect to the failed server since it
> doesn't
> exist and therefore will not delete the information from the DISTRIBUTOR.
> I would like to avoid manual system table clean up unless someone has the
> method that will completely remove this information.
> Is there a way to do this correctly?
> Thanks,
>
> Adam P. Cassidy
>