Msg 7391 and distributed transactions

Hi,
We are wondering what setting needs to be changed to get a large distributed
transaction to run.
We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that can
run a large distributed transaction to another W2K3 server, upgraded from
W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
did notice a difference in a setting for MSDTC that we made the same but
this has not worked.
Is there something that we missed because the new server is not an upgraded
W2K3 server from W2K?
Thanks
Chris Wood
Alberta Department of Energy
CANADA
See "How to enable network DTC access in Windows Server 2003"
http://support.microsoft.com/default...b;en-us;817064
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OsrpVxPvEHA.3424@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We are wondering what setting needs to be changed to get a large
> distributed
> transaction to run.
> We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that
> can
> run a large distributed transaction to another W2K3 server, upgraded from
> W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
> created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
> did notice a difference in a setting for MSDTC that we made the same but
> this has not worked.
> Is there something that we missed because the new server is not an
> upgraded
> W2K3 server from W2K?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>

Msg 7391 and distributed transactions

Hi,
We are wondering what setting needs to be changed to get a large distributed
transaction to run.
We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that can
run a large distributed transaction to another W2K3 server, upgraded from
W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
did notice a difference in a setting for MSDTC that we made the same but
this has not worked.
Is there something that we missed because the new server is not an upgraded
W2K3 server from W2K?
Thanks
Chris Wood
Alberta Department of Energy
CANADASee "How to enable network DTC access in Windows Server 2003"
http://support.microsoft.com/default.aspx?scid=kb;en-us;817064
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OsrpVxPvEHA.3424@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We are wondering what setting needs to be changed to get a large
> distributed
> transaction to run.
> We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that
> can
> run a large distributed transaction to another W2K3 server, upgraded from
> W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
> created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
> did notice a difference in a setting for MSDTC that we made the same but
> this has not worked.
> Is there something that we missed because the new server is not an
> upgraded
> W2K3 server from W2K?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>

Msg 7391 and distributed transactions

Hi,
We are wondering what setting needs to be changed to get a large distributed
transaction to run.
We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that can
run a large distributed transaction to another W2K3 server, upgraded from
W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
did notice a difference in a setting for MSDTC that we made the same but
this has not worked.
Is there something that we missed because the new server is not an upgraded
W2K3 server from W2K?
Thanks
Chris Wood
Alberta Department of Energy
CANADASee "How to enable network DTC access in Windows Server 2003"
http://support.microsoft.com/defaul...kb;en-us;817064
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:OsrpVxPvEHA.3424@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We are wondering what setting needs to be changed to get a large
> distributed
> transaction to run.
> We have a W2K3 server, upgraded from W2K with SQL2000 SP3A applied that
> can
> run a large distributed transaction to another W2K3 server, upgraded from
> W2K with SQL2000 SP3A applied. When we try the same transaction to a newly
> created W2K3 server with SQL2000 SP3A applied we get the 7391 message. We
> did notice a difference in a setting for MSDTC that we made the same but
> this has not worked.
> Is there something that we missed because the new server is not an
> upgraded
> W2K3 server from W2K?
> Thanks
> Chris Wood
> Alberta Department of Energy
> CANADA
>

MSDTC stopped working after reboot

I have:
w2k3 enterprise server
A/P Cluster
Sql 2000 sp4
All was well until we did a scheduled reboot. Now, DTS packages report that
the MSDTC is not running. I checked the Cluster Admin and services, all is
well.
I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
DNS, ETC. I ran these down and nothing is out of wack.
Any Ideas? Thanks!Hi
Did you try DTCPing? This may help
http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
John
"tbithoney" wrote:
> I have:
> w2k3 enterprise server
> A/P Cluster
> Sql 2000 sp4
> All was well until we did a scheduled reboot. Now, DTS packages report that
> the MSDTC is not running. I checked the Cluster Admin and services, all is
> well.
> I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> DNS, ETC. I ran these down and nothing is out of wack.
> Any Ideas? Thanks!
>|||Apparently, there is a HOTFIX for this issue.
the error is:
Server: Msg 8501, Level 16, State 3
As described in:
http://support.microsoft.com/default.aspx?scid=kb;en-us;889706
Have you tried this before?
"John Bell" wrote:
> Hi
> Did you try DTCPing? This may help
> http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
> John
> "tbithoney" wrote:
> > I have:
> > w2k3 enterprise server
> > A/P Cluster
> > Sql 2000 sp4
> >
> > All was well until we did a scheduled reboot. Now, DTS packages report that
> > the MSDTC is not running. I checked the Cluster Admin and services, all is
> > well.
> >
> > I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> > DNS, ETC. I ran these down and nothing is out of wack.
> >
> > Any Ideas? Thanks!
> >|||Hi
I have not tried this, it would be good practive to try it on a different
system first.
John
"tbithoney" wrote:
> Apparently, there is a HOTFIX for this issue.
> the error is:
> Server: Msg 8501, Level 16, State 3
> As described in:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889706
> Have you tried this before?
>
> "John Bell" wrote:
> > Hi
> >
> > Did you try DTCPing? This may help
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
> >
> > John
> >
> > "tbithoney" wrote:
> >
> > > I have:
> > > w2k3 enterprise server
> > > A/P Cluster
> > > Sql 2000 sp4
> > >
> > > All was well until we did a scheduled reboot. Now, DTS packages report that
> > > the MSDTC is not running. I checked the Cluster Admin and services, all is
> > > well.
> > >
> > > I down loaded the DTSTester, and it fails. Unable to attach. Mentions FW,
> > > DNS, ETC. I ran these down and nothing is out of wack.
> > >
> > > Any Ideas? Thanks!
> > >

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.

msdtc config / sql server 2k cluster(sp4) / W2k3 sp1

I have an application that uses com components to connect to it's backend sql
server db. Right now the db is running on a W2k server (sp4)
(non-clustered). I've copied the dbs to the clustered environment that we
are migrating all of our databases to, and now the com components do not
connect. I've installed the Network DTC components and have configured the
MSDTC resource via Cluster Adminstrator and can see that the service starts
on each server in the node as I fail the cluster group between those nodes.
I've read and adhered to doc 301600 and it's sub article of 817064
(pre-reqs). Not sure what else may be wrong or that I need to validate. The
application returns the following error when the user tries to login via the
web portal: New transaction cannot enlist in the specified transaction
coordinator. The application runs on a W2k (sp4) server. Any guidance would
be greatly appreciated.
It isn't anything to do with the cluster. This would happen on a stand-alone
system anyway.
HOWTO: Enable DTC Between Web Servers and SQL Servers Running Windows Server
2003
http://support.microsoft.com/default...b;en-us;555017
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LufkinTXDbajohn" <LufkinTXDbajohn@.discussions.microsoft.com> wrote in
message news:A0E2373E-5E90-45B2-B3EA-9BD32F6D4ABB@.microsoft.com...
>I have an application that uses com components to connect to it's backend
>sql
> server db. Right now the db is running on a W2k server (sp4)
> (non-clustered). I've copied the dbs to the clustered environment that we
> are migrating all of our databases to, and now the com components do not
> connect. I've installed the Network DTC components and have configured
> the
> MSDTC resource via Cluster Adminstrator and can see that the service
> starts
> on each server in the node as I fail the cluster group between those
> nodes.
> I've read and adhered to doc 301600 and it's sub article of 817064
> (pre-reqs). Not sure what else may be wrong or that I need to validate.
> The
> application returns the following error when the user tries to login via
> the
> web portal: New transaction cannot enlist in the specified transaction
> coordinator. The application runs on a W2k (sp4) server. Any guidance
> would
> be greatly appreciated.

MSDTC cannot move on a cluster

Today we installed on MS Cluster (W2k3) and SQL Server 2000 a MSDTC Service. The installation was succesfull, but wenn we try to move the group, then it failed. Because we have only 2 Disks on the cluster one for the Quorum, the other for the Sql Server. We installed the MSDTC as a Resource on the Quorum Disk. The other Thing, wenn we start the firts node all is running on the first node, but we cannot move. Wenn we start the second node all is running on the second node, but we cannot move the Group which contain the Msdtc resource.

Who has a solution to this problem?

Thanks to all

Did you run comclust.exe on each of the nodes before installing SQL Server?

MSDTC and W2K3

I've read about a thousand different things and really need a straight answer:
I'm setting up clustering on a dual-node W2K3 cluster.
If the applications that are accessing the SQL Server DO NOT utilize MSDTC,
do I need to even bother with creating the group, resources, etc. for MSDTC?
If I still need to create it, exactly what is the Network Resoource name:
just some random name I make up or is it something specific?
And doesn't SQL Server install create those anywway?
Thanks for any help you can provide.
Anthony
SQL does not require MSDTC, if you app does not use it, don't install it.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"A. Robinson" <A. Robinson@.discussions.microsoft.com> wrote in message
news:6B0E7A37-47B3-475D-81AE-FE0C4E49E900@.microsoft.com...
> I've read about a thousand different things and really need a straight
> answer:
> I'm setting up clustering on a dual-node W2K3 cluster.
> If the applications that are accessing the SQL Server DO NOT utilize
> MSDTC,
> do I need to even bother with creating the group, resources, etc. for
> MSDTC?
> If I still need to create it, exactly what is the Network Resoource name:
> just some random name I make up or is it something specific?
> And doesn't SQL Server install create those anywway?
> Thanks for any help you can provide.
> Anthony
|||Thank you!!! Was going nuts trying to convince people it didn't need to be
there if you don't use it...
"Rodney R. Fournier [MVP]" wrote:

> SQL does not require MSDTC, if you app does not use it, don't install it.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "A. Robinson" <A. Robinson@.discussions.microsoft.com> wrote in message
> news:6B0E7A37-47B3-475D-81AE-FE0C4E49E900@.microsoft.com...
>
>
|||If you won't be using it heavily, I would still set it up using in the
cluster group using the Quorum disk. I personally have had zero success
installing a clustered SQL 2000 without MSDTC.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:EEB3C7D5-974C-4CDB-9C82-69230336BA96@.microsoft.com...[vbcol=seagreen]
> Thank you!!! Was going nuts trying to convince people it didn't need to be
> there if you don't use it...
> "Rodney R. Fournier [MVP]" wrote:
it.[vbcol=seagreen]
name:[vbcol=seagreen]
|||Really? We have 20 of them. They all work great.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Qim8SkJFHA.3340@.TK2MSFTNGP14.phx.gbl...
> If you won't be using it heavily, I would still set it up using in the
> cluster group using the Quorum disk. I personally have had zero success
> installing a clustered SQL 2000 without MSDTC.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:EEB3C7D5-974C-4CDB-9C82-69230336BA96@.microsoft.com...
> it.
> name:
>
|||While SQL Server does not require MS DTC, MS DTC on a cluster is only
supported when clustered and it is recommended to cluster it.
When clustering MS DTC it is preferred to have it in its own group with its
own resources, your second choice should be to put it in the cluster group,
use the quorum disk and create MS DTC its own Network Name and IP Address
resources for your MSDTC resource to use and set that resources properties
not to affect the group.
Here are some KB articles on correctly setting this up:
301600 How to configure Microsoft Distributed Transaction Coordinator on a
http://support.microsoft.com/?id=301600
817064 How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/?id=817064
Also this article which may be of interest:
817065 How To Enable Network COM Access in Windows Server 2003
http://support.microsoft.com/?id=817065
Dave Whitney
SQL Support
|||Agreed, since we use SQL clusters without MSDTC, we disable the default
windows service for it.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"Dave Whitney [MS]" <dwhitneyOnline@.microsoft.com> wrote in message
news:FEBotroJFHA.132@.TK2MSFTNGXA02.phx.gbl...
> While SQL Server does not require MS DTC, MS DTC on a cluster is only
> supported when clustered and it is recommended to cluster it.
> When clustering MS DTC it is preferred to have it in its own group with
> its
> own resources, your second choice should be to put it in the cluster
> group,
> use the quorum disk and create MS DTC its own Network Name and IP Address
> resources for your MSDTC resource to use and set that resources properties
> not to affect the group.
> Here are some KB articles on correctly setting this up:
> 301600 How to configure Microsoft Distributed Transaction Coordinator on a
> http://support.microsoft.com/?id=301600
> 817064 How to enable network DTC access in Windows Server 2003
> http://support.microsoft.com/?id=817064
> Also this article which may be of interest:
> 817065 How To Enable Network COM Access in Windows Server 2003
> http://support.microsoft.com/?id=817065
> Dave Whitney
> SQL Support
>
|||Well, we have been scared by the recommended best practices into submission,
and simply sucked in and coughed up a separate disk for the MSDTC resource.
(I'm not talking about whether the MSDTC resource should or should not be
configured. It should in our environments.)
Linchi
"Dave Whitney [MS]" <dwhitneyOnline@.microsoft.com> wrote in message
news:FEBotroJFHA.132@.TK2MSFTNGXA02.phx.gbl...
> While SQL Server does not require MS DTC, MS DTC on a cluster is only
> supported when clustered and it is recommended to cluster it.
> When clustering MS DTC it is preferred to have it in its own group with
> its
> own resources, your second choice should be to put it in the cluster
> group,
> use the quorum disk and create MS DTC its own Network Name and IP Address
> resources for your MSDTC resource to use and set that resources properties
> not to affect the group.
> Here are some KB articles on correctly setting this up:
> 301600 How to configure Microsoft Distributed Transaction Coordinator on a
> http://support.microsoft.com/?id=301600
> 817064 How to enable network DTC access in Windows Server 2003
> http://support.microsoft.com/?id=817064
> Also this article which may be of interest:
> 817065 How To Enable Network COM Access in Windows Server 2003
> http://support.microsoft.com/?id=817065
> Dave Whitney
> SQL Support
>

MSDTC / W2K3 / SQL 2000 Clustering

I'm in the process of setting up my first W2K3 / SQL 2000 cluster and I have a few questions with regards to MSDTC.
Documentation I have says that MSDTC must be clustered in order for SQL clustering to work. It also says that you cannot use comclust.exe anymore and that MSDTC must be setup in its own group with the following ( VIP, Network Name, and dedicated shared di
sk). I currently have Windows and SQL 2000 clustering up and running without MSDTC clustered.
My questions are :
1) Do I need MSDTC at all? If so, why?
2) If I do need MSDTC clustered, can I use a disk that has other applications installed on it? (I only have two LUNS to work with on the SAN, my quorum device and a device I'm using for SQL data / logs)
I know that I haven't given a lot of background information, but I was hoping I could get a discussion started.
Thanks.
Comments inline.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"tech_arch_guy" <tech_arch_guy@.discussions.microsoft.com> wrote in message
news:2B8AD70E-877C-4F02-A0F7-7A51B072075C@.microsoft.com...
> I'm in the process of setting up my first W2K3 / SQL 2000 cluster and I
have a few questions with regards to MSDTC.
> Documentation I have says that MSDTC must be clustered in order for SQL
clustering to work. It also says that you cannot use comclust.exe anymore
and that MSDTC must be setup in its own group with the following ( VIP,
Network Name, and dedicated shared disk). I currently have Windows and SQL
2000 clustering up and running without MSDTC clustered.
> My questions are :
> 1) Do I need MSDTC at all? If so, why?
Yes. Setup will fail without MSDTC.
> 2) If I do need MSDTC clustered, can I use a disk that has other
applications installed on it? (I only have two LUNS to work with on the SAN,
my quorum device and a device I'm using for SQL data / logs)
>
W2000 used the quorum device as the MSDTC physical disk by default. W2003
recommends using another disk, but in your case the qourum drive is probably
OK. I have a cluster upgraded from W2000 to W2003 with MSDTC on the quorum
device and it works just fine.

> I know that I haven't given a lot of background information, but I was
hoping I could get a discussion started.
> Thanks.
|||You do NOT need MSDTC clustered for installing SQL Server 2000 virtual instance on a Windows 2003 Microsoft Cluster Server. You need MSDTC only if you doing distributed transactions. you can cluster MSDTC
even after installing SQL Server 2000 virtual instance.
Refer the foll. KB for Win2K3
How to configure Microsoft Distributed Transaction Coordinator (MSDTC)on a Windows Server 2003
http://support.microsoft.com/?kbid=301600
How to enable network DTC access in Windows Server 2003
http://support.microsoft.com/default.aspx?kbid=817064
It is recommended to use a seperate shared disk (500MB works) for MSDTC. In your case you just have the qourum disk and sql disk. I have seen many clusters that have MSDTC using the Quorum disk. Usually if
you are not doing a lot of distributed transactions then leave that way if everything is working fine. But if you are building your cluster and want to build as per best practices then the recommendation is to use a
seperate disk for MSDTC.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||I agree with Uttam but if you like to create DTC resource if you have
distributed transactions or even linked servers, you will be creating it just
like you create a disk resource. Make sure you have a disk, name and ip
resource created for MSDTC.
"Uttam Parui[MS]" wrote:

> You do NOT need MSDTC clustered for installing SQL Server 2000 virtual instance on a Windows 2003 Microsoft Cluster Server. You need MSDTC only if you doing distributed transactions. you can cluster MSDTC
> even after installing SQL Server 2000 virtual instance.
> Refer the foll. KB for Win2K3
> How to configure Microsoft Distributed Transaction Coordinator (MSDTC)on a Windows Server 2003
> http://support.microsoft.com/?kbid=301600
> How to enable network DTC access in Windows Server 2003
> http://support.microsoft.com/default.aspx?kbid=817064
> It is recommended to use a seperate shared disk (500MB works) for MSDTC. In your case you just have the qourum disk and sql disk. I have seen many clusters that have MSDTC using the Quorum disk. Usually if
> you are not doing a lot of distributed transactions then leave that way if everything is working fine. But if you are building your cluster and want to build as per best practices then the recommendation is to use a
> seperate disk for MSDTC.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>

MSDTC & W2K3 & SQL 2000 issue

I have MSDTC installed in the Cluster group (no other disks available). It fails over fine, comes online on either node, no problem. My DBA alerted me, that she cannot start Distributed Transaction Coordinator on the node that is NOT in control of the MSD
TC resource using SQL Server Enterprise Manager. This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA) CAN start MSDTC on either/both nodes of the W2K cluster. W
hy won't DTC start on the other node in Ent Mgr? The DBA says that this is necessary for something to function correctly, so I have to fix it? Any ideas/help would be appreciated.
A clustered instance of SQL server uses a cluster-wide MSDTC instance
instead of a local MSDTC instance on each host node. As such, the cluster
admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
Mangler. So, the behavior your DBA noted is correct for a cluster, but
since MSDTC is running the application will function correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"wbielinski at abms dot org" <wbielinski at abms dot
org@.discussions.microsoft.com> wrote in message
news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> I have MSDTC installed in the Cluster group (no other disks available). It
fails over fine, comes online on either node, no problem. My DBA alerted me,
that she cannot start Distributed Transaction Coordinator on the node that
is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
start on the other node in Ent Mgr? The DBA says that this is necessary for
something to function correctly, so I have to fix it? Any ideas/help would
be appreciated.
|||It is a good idea to place MSDTC in its own resource group and another thing
I will check is that the Network access for DTC is enabled. YOu can look for
this in control panel/add remove programs/add remove components/Application
Server.
"Geoff N. Hiten" wrote:

> A clustered instance of SQL server uses a cluster-wide MSDTC instance
> instead of a local MSDTC instance on each host node. As such, the cluster
> admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
> Mangler. So, the behavior your DBA noted is correct for a cluster, but
> since MSDTC is running the application will function correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "wbielinski at abms dot org" <wbielinski at abms dot
> org@.discussions.microsoft.com> wrote in message
> news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> fails over fine, comes online on either node, no problem. My DBA alerted me,
> that she cannot start Distributed Transaction Coordinator on the node that
> is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
> This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
> configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
> CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
> start on the other node in Ent Mgr? The DBA says that this is necessary for
> something to function correctly, so I have to fix it? Any ideas/help would
> be appreciated.
>
>