MSDTC Problem

Hi,

I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?

Thanks

Server: Msg 7391, Level 16, State 1, Line 1
The 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].Thanks in advance for any help you can offer.

I have same problem as cpyne.

I recently upgraded a SQL server 7.0 box to SQL server 2000.
(Standard edition)

I had several stored procs selecting data from linked servers and inserting into local tables.

They all ran fine for the last 2 years but after the upgrade they all fail.
Linked servers include SQL Server, ORACLE and INFORMIX databases.

Error report indicates that MSDTC is now unable to begin distributed transaction.

Anybody know why MSDTC is suddenly failing after I switched from version 7 to 2000?|||On most of our servers that had this problem, MSDTC was stopped on the remote server. Starting it and setting it to automatic fixed the issue. There were a few queries that didn't even appear to be distributed transactions. They were just local tables with joins to linked servers. I spoke with MS about this and they said that SQL 2000 makes more use for MSDTC in places where SQL 7.0 didn't. The only servers where we had difficulty getting this working were ones where there was a firewall between the master server and the linked ones. In the end we dicided to chang the logic of our application, but MS suggested some articles that listed which ports needed to be opened. I don't have them handy, but if you have this problem, search on Firewall and MSDTC.

Charlie

msdtc is causing my cluster to be unavailiable via it's virtual na

I have windows 2003 sp1 running in a 2-node cluster. The cluster is running
sql sp4. I tried failing over my cluster after a windows update and i'm not
sure if that's what threw my server's off or something else. But here's the
situation. I currently have the cluster group running on node 2, the msdtc
running on node 1 and the sql group running on node 2. When i move the msdtc
group to node 2 (ie.. the server which should be running all services)i cant
ping the sql virtual server by name or ip. I am however able to contact the
individual servers via their names sql1 and sql2. So basically i lose my
connection to the virtual sql server throughout my network when the msdtc is
running on the same server. Is there an update? upgrade? to the msdtc or
anything else i can do to fix this issue?
Ohh yes and there's no errors in the event log.
What are the Resource Group names, Resource Network Names, and Resource IP
addresses? What other resources a apart of each group?
Sounds like a DNS registration issue. Does the SQL Server group go offline
or fail over when the MSDTC group is moved to node 2?
Sincerely,
Anthony Thomas

"Sunny" <Sunny@.discussions.microsoft.com> wrote in message
news:12879549-04B5-454B-A44C-C075061EAEC1@.microsoft.com...
> I have windows 2003 sp1 running in a 2-node cluster. The cluster is
running
> sql sp4. I tried failing over my cluster after a windows update and i'm
not
> sure if that's what threw my server's off or something else. But here's
the
> situation. I currently have the cluster group running on node 2, the
msdtc
> running on node 1 and the sql group running on node 2. When i move the
msdtc
> group to node 2 (ie.. the server which should be running all services)i
cant
> ping the sql virtual server by name or ip. I am however able to contact
the
> individual servers via their names sql1 and sql2. So basically i lose my
> connection to the virtual sql server throughout my network when the msdtc
is
> running on the same server. Is there an update? upgrade? to the msdtc or
> anything else i can do to fix this issue?
> Ohh yes and there's no errors in the event log.

MSDTC fails on Windows 2003 but security has been reset so its not that.

I am running SQL Server 2000 (clustered server) with Windows 2003. For some reason MSDTC is failing on distributed transactions. I can run code that begins and commits a transaction from query analyzer, or run a stored procedure from Query Analyzer with the same code in it and both work great, but if I call the stored procedure from a DTS job, then the job fails with the following error:

DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14) Error string: The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. Error source: ..... Error string: OLE DB error trace [OLE/DB Provider 'MSDASQL' ITransactionJoin::JoinTransaction returned 0x8004d00a]. Error source: Microsoft OLE DB Provider for SQL Serve. The step failed.

Any help would be appreciated!Ensure MSDTC is started on the machine.
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3451 for your reference.