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
Showing posts with label moved. Show all posts
Showing posts with label moved. Show all posts
Wednesday, March 7, 2012
Saturday, February 25, 2012
MSDTC doesn't work on SQL 2k in W2k3 cluster environment
Hi,
I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1
cluster server recently. After the move, I found two applications that use
MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I
didn't enable network DTC access on both nodes before I configured MSDTC and
then installed the SQL server. To remedy this problem, I deleted the MSDTC
resource in the cluster admin, and reconfigured it again after enable the
network DTC access on both nodes. However, the MSDTC on the cluster still
doesn't work. The installation sequence should configure MSDTC first, then
install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
server to get MSDTC work?
I use DTCTester and get following error:
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
Driver][SQL Se
rver]MSDTC on server 'AWIDB1' is unavailable.'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.
Thanks in advance.
Never mind. it worked. I should restart the SQL server after re-configured
the MSDTC resource. Since this server has been in production already, I just
wished that every changes would take effect dynamically.
"Jack Zhang" wrote:
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
|||You are correct in that you should have followed the correct and documented
installation sequence; however, you should be able to do it after the fact.
Also know that there is a COM 1.5 bug in Windows 2003.
First, after reclustering the MSDTC, did you configure it within its own
dedicated Cluster Resource Group? It will require the creation of this
group, a dedicated SAN disk, IP, and Network Name cluster resources. Then,
you will need to fail that resource back and forth between the nodes to get
the resource registry entries to synchronize.
You will then need to take the SQL Server IP resource offline, which should
bring the resources in that group offline and then bring the group back
online.
In the SQL Server Error Log, you will see SQL Server attempting to connect
to the DTC resource; if it opens the connection, there will be no additional
messages. If it has a problem however, it will spit out a "Could not
generate resource context" type of error message. That will tell you if
this worked or not.
If this process fails, one other option would be to run through the ADVANCED
section of the SQL Server installation processes. This should
verify/generate the necessary registry key dependencies without having to
completely reinstall.
If this too does not solve the problem, then before you uninstall/reinstall,
I would seriously consider opening a Microsoft Product Support Services
case, MS PSS.
INFO: Availability of Windows Server 2003 COM+ 1.5 Rollup Package 1
http://support.microsoft.com/kb/821751/
You receive error messages when you perform a distributed transaction when
you have a SQL Server 2000 virtual server in a Windows Server 2003 clustered
environment
http://support.microsoft.com/default...b;en-us;889706
How to rebuild or move MSDTC used with a SQL failover cluster
http://support.microsoft.com/default...b;en-us;294209
How to configure Microsoft Distributed Transaction Coordinator on a Windows
Server 2003 cluster
http://support.microsoft.com/kb/301600/
How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/kb/817064/
Good luck and be sure to let us know how it turns out.
Sincerely,
Anthony Thomas
"Jack Zhang" <JackZhang@.discussions.microsoft.com> wrote in message
news:46C965C9-5431-460C-92ED-DE5873B57E2F@.microsoft.com...
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3
SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the
MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC
and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
|||Did you set the security on MSDTC through the Component Services Applet?
That is a necessary step after all the steps you listed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jack Zhang" <JackZhang@.discussions.microsoft.com> wrote in message
news:46C965C9-5431-460C-92ED-DE5873B57E2F@.microsoft.com...
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3
> SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the
> MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC
> and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
> Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1
cluster server recently. After the move, I found two applications that use
MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I
didn't enable network DTC access on both nodes before I configured MSDTC and
then installed the SQL server. To remedy this problem, I deleted the MSDTC
resource in the cluster admin, and reconfigured it again after enable the
network DTC access on both nodes. However, the MSDTC on the cluster still
doesn't work. The installation sequence should configure MSDTC first, then
install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
server to get MSDTC work?
I use DTCTester and get following error:
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
Driver][SQL Se
rver]MSDTC on server 'AWIDB1' is unavailable.'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.
Thanks in advance.
Never mind. it worked. I should restart the SQL server after re-configured
the MSDTC resource. Since this server has been in production already, I just
wished that every changes would take effect dynamically.
"Jack Zhang" wrote:
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
|||You are correct in that you should have followed the correct and documented
installation sequence; however, you should be able to do it after the fact.
Also know that there is a COM 1.5 bug in Windows 2003.
First, after reclustering the MSDTC, did you configure it within its own
dedicated Cluster Resource Group? It will require the creation of this
group, a dedicated SAN disk, IP, and Network Name cluster resources. Then,
you will need to fail that resource back and forth between the nodes to get
the resource registry entries to synchronize.
You will then need to take the SQL Server IP resource offline, which should
bring the resources in that group offline and then bring the group back
online.
In the SQL Server Error Log, you will see SQL Server attempting to connect
to the DTC resource; if it opens the connection, there will be no additional
messages. If it has a problem however, it will spit out a "Could not
generate resource context" type of error message. That will tell you if
this worked or not.
If this process fails, one other option would be to run through the ADVANCED
section of the SQL Server installation processes. This should
verify/generate the necessary registry key dependencies without having to
completely reinstall.
If this too does not solve the problem, then before you uninstall/reinstall,
I would seriously consider opening a Microsoft Product Support Services
case, MS PSS.
INFO: Availability of Windows Server 2003 COM+ 1.5 Rollup Package 1
http://support.microsoft.com/kb/821751/
You receive error messages when you perform a distributed transaction when
you have a SQL Server 2000 virtual server in a Windows Server 2003 clustered
environment
http://support.microsoft.com/default...b;en-us;889706
How to rebuild or move MSDTC used with a SQL failover cluster
http://support.microsoft.com/default...b;en-us;294209
How to configure Microsoft Distributed Transaction Coordinator on a Windows
Server 2003 cluster
http://support.microsoft.com/kb/301600/
How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/kb/817064/
Good luck and be sure to let us know how it turns out.
Sincerely,
Anthony Thomas
"Jack Zhang" <JackZhang@.discussions.microsoft.com> wrote in message
news:46C965C9-5431-460C-92ED-DE5873B57E2F@.microsoft.com...
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3
SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the
MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC
and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
|||Did you set the security on MSDTC through the Component Services Applet?
That is a necessary step after all the steps you listed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jack Zhang" <JackZhang@.discussions.microsoft.com> wrote in message
news:46C965C9-5431-460C-92ED-DE5873B57E2F@.microsoft.com...
> Hi,
> I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3
> SP1
> cluster server recently. After the move, I found two applications that use
> MSDTC didn't work. I realized that I made a mistake when I setup the
> MSDTC, I
> didn't enable network DTC access on both nodes before I configured MSDTC
> and
> then installed the SQL server. To remedy this problem, I deleted the MSDTC
> resource in the cluster admin, and reconfigured it again after enable the
> network DTC access on both nodes. However, the MSDTC on the cluster still
> doesn't work. The installation sequence should configure MSDTC first, then
> install SQL2K. Does this sequence matter? Do I have to reinstall the SQL
> server to get MSDTC work?
> I use DTCTester and get following error:
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server
> Driver][SQL Se
> rver]MSDTC on server 'AWIDB1' is unavailable.'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
> Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
> Thanks in advance.
Labels:
applications,
cluster,
database,
environment,
microsoft,
moved,
msdtc,
mysql,
oracle,
server,
sp1cluster,
sql,
w2k,
w2k3
Subscribe to:
Posts (Atom)