Re: Error on updatable subscription

Were any of the tables owned by different object owners and did you change
the object owners at any point in time?

--
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
"Sam" <z.sam-No-Spam-@xxxxxxxxx> wrote in message
news:%232Ap103lFHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
> After a lot of troubles I make working the Transaction Replication between
2
> pc.
> The replication is transaction with updatable subriber with update
> subscription and queue update on failover.
>
> While it works well if the connection between the two pc is ok, if I
> disconnect the subscriber from the network and try to make a update on a
> table I receive this message:
>
> ---------------------------
> SQL Server Enterprise Manager
> ---------------------------
> Another user has modified the contents of this table or view; the database
> row you are modifying no longer exists in the database.
>
> Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
> provider returned message: Connection failure]
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c].
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction.'
>
>
> The table has a primary key which is of type identity, both on the
publisher
> and subcriber, then there is a column of type guid for replication.
> I don't need to do insert on the subscription but only update.
>
> Thanks in advance.
>
>


.

Relevant Pages

  • Error on updatable subscription
    ... After a lot of troubles I make working the Transaction Replication between 2 ... Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c]. ... I don't need to do insert on the subscription but only update. ...
    (microsoft.public.sqlserver.replication)
  • Re: Host Name Change and Replication
    ... the msdb.sysjobs did still contain PDB01 as the server originator and this caused the 14274 error about the MSX. ... I then added accountName user to the Security folder again, reenabled replication, and then made sure each agent was using the accountName and tested the replication. ... Unfortunately on DGP09 and TDB10 in their> subscription folder each had a push subscription pointing to PDB01 which no> longer exsists. ...
    (microsoft.public.sqlserver.server)
  • Re: General SQL Server 2005 transactional replication question
    ... "Hilary Cotter" wrote: ... Looking for a SQL Server replication book? ... publication part that requires the primary key constraints rather than the ... create the publication on the publisher and create the subscription, ...
    (microsoft.public.sqlserver.replication)
  • Re: General SQL Server 2005 transactional replication question
    ... I would evaluate whether you can change your unique indexes into real PKs. ... Looking for a SQL Server replication book? ... database makes little use of primary key constraints (just uses unique ... create the publication on the publisher and create the subscription, ...
    (microsoft.public.sqlserver.replication)
  • Re: General SQL Server 2005 transactional replication question
    ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... database makes little use of primary key constraints (just uses unique ... subscription side per se, so this would rule out things like using ...
    (microsoft.public.sqlserver.replication)