UPDATABLE TRANSACCIONAL

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jose Fernandez - 25 Feb 2006 21:33 GMT

Hello.

I have a new issue...

I created a publication. It's a Updatable Transaccional Inmediate Updating
replication.

My C.S.I. is:

I have 4 workstation with a localhost web application (subscribers). I have
1 server (Publisher). When I try to enter some data on the subscriber it
comes out the error MSDTC on server "XXX" is unavailable (XXX is the name of
the subscriber).

What should I do about it?

Thanks in advance

Reply to this Message

Hilary Cotter - 26 Feb 2006 18:13 GMT

Is the publisher online and accessible? If not you will get this error. I
would use queued or merge over immediate updating unless you know your link
will always be up.

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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

> Hello.
>
[quoted text clipped - 14 lines]
>
> Thanks in advance

Reply to this Message

Jose Fernandez - 27 Feb 2006 17:17 GMT

Well... I was looking on internet.

I found that I had to do some work on Administratives Tools (Components
Services) like activate MSDTC. I read some documentation about it. But i
keep getting error. Now is a different one.

he operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. [OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].

I found this article... http://support.microsoft.com/?kbid=839279

I made it all... Nothing. Still getting the same error

> Is the publisher online and accessible? If not you will get this error. I
> would use queued or merge over immediate updating unless you know your
[quoted text clipped - 19 lines]
>>
>> Thanks in advance

Reply to this Message

Jose Fernandez - 27 Feb 2006 23:50 GMT

Well...

i made a new publication. Queue updatable one.

Now, everything was going ok until a delete statement was thrown.

here is the error

Category:COMMAND
Source: Failed Command
Number:
Message: {CALL sp_MSdel_deportes ('ESN', '', 'Esquí Náutico', 'Water Ski',
1, 1, 1, 1, 1, 1, 0, {D7A8B11C-E1BE-412C-9D12-747A73F63D3A})}

Category:SQLSERVER
Source: PPCUBAN
Number: 547
Message: DELETE statement conflicted with COLUMN REFERENCE constraint
'FK_eventos_deportes'. The conflict occurred in database 'historia', table
'eventos', column 'sigDeporte'.

I can't find what to do to solve this issue and continue replicating. It
just stopped.

Any suggestion?

Reply to this Message