Is it possible to upgrade about 80 clients from SQL 7 client to SQL 2000
client automatically using group policy push and msi technology?
Aswered in .clients "Subject: SQL 7 to 2K client upgrade"
"Dex Dexter" wrote:
> Is it possible to upgrade about 80 clients from SQL 7 client to SQL 2000
> client automatically using group policy push and msi technology?
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Wednesday, March 21, 2012
Wednesday, March 7, 2012
MSDTC Resource on Win2003 cluster
I am having trouble to fail over MSDTC Resource group to a second node in a two node cluster. It is running fine on the first node but refuse to start on the second node.
Any help will be greatly appreciated.
Yuhong
yuhong.huo@.yale.edu
I found the solution. Just want post it here in case anybody run into the same problem.
I took the MSDTC Cluster Group offline on the first node and ran msdtc.exe -resetlog command on the second node. And it worked. See article: http://support.microsoft.com/?kbid=243204
Yuhong
|||You may want to check kb article..
http://support.microsoft.com/default...b;EN-US;248025
Van Thothathri
Windows Clustering
High Availability Microsoft Enterprise Server Products
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
"Yuhong Huo" <anonymous@.discussions.microsoft.com> wrote in message
news:EEA345EC-A673-48A9-8E61-2580049D5F14@.microsoft.com...
>I am having trouble to fail over MSDTC Resource group to a second node in a
>two node cluster. It is running fine on the first node but refuse to start
>on the second node.
> Any help will be greatly appreciated.
> Yuhong
> yuhong.huo@.yale.edu
Any help will be greatly appreciated.
Yuhong
yuhong.huo@.yale.edu
I found the solution. Just want post it here in case anybody run into the same problem.
I took the MSDTC Cluster Group offline on the first node and ran msdtc.exe -resetlog command on the second node. And it worked. See article: http://support.microsoft.com/?kbid=243204
Yuhong
|||You may want to check kb article..
http://support.microsoft.com/default...b;EN-US;248025
Van Thothathri
Windows Clustering
High Availability Microsoft Enterprise Server Products
"This posting is provided "AS IS" with no warranties, and confers no
rights."
Use of included script samples, if any, are subject to the terms specified
at http://www.microsoft.com/info/cpyright.htm
"Yuhong Huo" <anonymous@.discussions.microsoft.com> wrote in message
news:EEA345EC-A673-48A9-8E61-2580049D5F14@.microsoft.com...
>I am having trouble to fail over MSDTC Resource group to a second node in a
>two node cluster. It is running fine on the first node but refuse to start
>on the second node.
> Any help will be greatly appreciated.
> Yuhong
> yuhong.huo@.yale.edu
MSDTC Resource in the Cluster Group
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
It's more a matter of usage and availability. If you use it a lot, even
though its small, it takes it toll on the disk. You would never want MSDTC
to take cycles away from what the quorum is trying to use. As for
availability, what happens if you have a resource failure? By default, the
group is afftected. Putting more things in ANY group, affects the group as a
whole. For the Highest Availability, keep everything separate.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:E91F75E1-1006-4062-8BC7-35D94FD3E77F@.microsoft.com...
> Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
> if
> the MSDTC has its own IP Address and Network Name?
> In my planned multiple instance sql cluster, I can see giving up a
> physical
> disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
> doesn't use tons on disk space, can I put it in the same group as the
> defualt
> instance of SQL, again as long has it has its own IP Address and Network
> Name?
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
It's more a matter of usage and availability. If you use it a lot, even
though its small, it takes it toll on the disk. You would never want MSDTC
to take cycles away from what the quorum is trying to use. As for
availability, what happens if you have a resource failure? By default, the
group is afftected. Putting more things in ANY group, affects the group as a
whole. For the Highest Availability, keep everything separate.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:E91F75E1-1006-4062-8BC7-35D94FD3E77F@.microsoft.com...
> Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
> if
> the MSDTC has its own IP Address and Network Name?
> In my planned multiple instance sql cluster, I can see giving up a
> physical
> disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
> doesn't use tons on disk space, can I put it in the same group as the
> defualt
> instance of SQL, again as long has it has its own IP Address and Network
> Name?
MSDTC Resource Group - Physical Disk and Network Name
Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
MSDTC should be in its own resource group.
- What is the recommended size for the physical disk that needs to be in
this resource group?
- Is it necessary to add the Network Name resource to DNS?
Thank you.
500 MB (meg) or bigger.
You will need an IP and Network Name for it to be on the wire.
If you are running Windows Sever 2003, be sure to follow 817064 FIRST.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"vkb" <vkb@.discussions.microsoft.com> wrote in message
news:48A5C66D-988B-47A1-B638-DA2FC15AEB9B@.microsoft.com...
> Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
> MSDTC should be in its own resource group.
> - What is the recommended size for the physical disk that needs to be in
> this resource group?
> - Is it necessary to add the Network Name resource to DNS?
> Thank you.
MSDTC should be in its own resource group.
- What is the recommended size for the physical disk that needs to be in
this resource group?
- Is it necessary to add the Network Name resource to DNS?
Thank you.
500 MB (meg) or bigger.
You will need an IP and Network Name for it to be on the wire.
If you are running Windows Sever 2003, be sure to follow 817064 FIRST.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"vkb" <vkb@.discussions.microsoft.com> wrote in message
news:48A5C66D-988B-47A1-B638-DA2FC15AEB9B@.microsoft.com...
> Article 301600 (http://support.microsoft.com/?kbid=301600) mentions that
> MSDTC should be in its own resource group.
> - What is the recommended size for the physical disk that needs to be in
> this resource group?
> - Is it necessary to add the Network Name resource to DNS?
> Thank you.
Saturday, February 25, 2012
MSDTC in Default Cluster Group
Hi,
Can I put the MSDTC resource in Defaul Cluster Group ? I dont have available
disk to it.
thanks,
Rubens
Yes, you can put it in this group, but this goes against best practices. You
might want to consider unchecking the "affect the group" paramter for this
resource so a failure of this resource does not kill your cluster group.
Regards,
John
"Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Can I put the MSDTC resource in Defaul Cluster Group ? I dont have
available
> disk to it.
> thanks,
> Rubens
>
|||If one node fail,can msdtc resource automatically move to another node?
Could you tell me more information about following line?
You might want to consider unchecking the "affect the group" paramter for
this resource so a failure of this resource does not kill your cluster
group.
"John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org> д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...
> Yes, you can put it in this group, but this goes against best practices.
> You
> might want to consider unchecking the "affect the group" paramter for this
> resource so a failure of this resource does not kill your cluster group.
> Regards,
> John
> "Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
> news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> available
>
|||Yes, please read through the following KB article for more details about
setting up MSDTC resource in the cluster.
http://support.microsoft.com/kb/301600
Regards,
John
"lv ming tong" <lmt@.taeco.com.diss> wrote in message
news:uTuiBG3IFHA.1304@.TK2MSFTNGP09.phx.gbl...
> If one node fail,can msdtc resource automatically move to another node?
> Could you tell me more information about following line?
> You might want to consider unchecking the "affect the group" paramter for
> this resource so a failure of this resource does not kill your cluster
> group.
>
> "John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org>
д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...[vbcol=seagreen]
this
>
|||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
Can I put the MSDTC resource in Defaul Cluster Group ? I dont have available
disk to it.
thanks,
Rubens
Yes, you can put it in this group, but this goes against best practices. You
might want to consider unchecking the "affect the group" paramter for this
resource so a failure of this resource does not kill your cluster group.
Regards,
John
"Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> Hi,
> Can I put the MSDTC resource in Defaul Cluster Group ? I dont have
available
> disk to it.
> thanks,
> Rubens
>
|||If one node fail,can msdtc resource automatically move to another node?
Could you tell me more information about following line?
You might want to consider unchecking the "affect the group" paramter for
this resource so a failure of this resource does not kill your cluster
group.
"John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org> д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...
> Yes, you can put it in this group, but this goes against best practices.
> You
> might want to consider unchecking the "affect the group" paramter for this
> resource so a failure of this resource does not kill your cluster group.
> Regards,
> John
> "Rubens Luque Sanches Jr." <rubensluque@.yahoo.com.br> wrote in message
> news:eQeH1N4HFHA.2784@.TK2MSFTNGP09.phx.gbl...
> available
>
|||Yes, please read through the following KB article for more details about
setting up MSDTC resource in the cluster.
http://support.microsoft.com/kb/301600
Regards,
John
"lv ming tong" <lmt@.taeco.com.diss> wrote in message
news:uTuiBG3IFHA.1304@.TK2MSFTNGP09.phx.gbl...
> If one node fail,can msdtc resource automatically move to another node?
> Could you tell me more information about following line?
> You might want to consider unchecking the "affect the group" paramter for
> this resource so a failure of this resource does not kill your cluster
> group.
>
> "John Toner [MVP]" <jtoner@.DIE.SPAM.DIE.mvps.org>
д?:%23i%23CfY$HFHA.588@.TK2MSFTNGP15.phx. gbl...[vbcol=seagreen]
this
>
|||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 in Cluster Group
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
MSDTC in Cluster Group
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?The original MS KB posts recommended using the Cluster Group resource;
however, we've found out that it does not work and an instance of SQL Server
can not bind to it unless it's on the same node.
You can put it in the SQL Server Group resource, but it won't work once you
go multi-instanced. At that point, MS recommends that you create a seperate
shared disk resource with its own IP and Network Name resources and cluster
MS DTC as a seperate group. Looks like the coders didn't think through the
implications of the Quorum and coded against it. The SQL Server
developement group did not realize this.
Sincerely,
Anthony Thomas
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:922FDA87-A645-43C7-8442-BAD97525A3F1@.microsoft.com...
Why is it a bad idea to have the MSDTC Resource in the Cluster Group, even
if
the MSDTC has its own IP Address and Network Name?
In my planned multiple instance sql cluster, I can see giving up a physical
disk to the Quarum, but another disk to MSTDC as well. Since the MSTDC
doesn't use tons on disk space, can I put it in the same group as the
defualt
instance of SQL, again as long has it has its own IP Address and Network
Name?
MSDTC Group
I have the MSDTC group with resources in a SQL Server cluster.
The MSDTC group and resources are all online from Cluster Administrator. If
check SQL Server Support Service it show the service as stopped. The Server
services shows the MSDTC to off.
Please help me with these results.
1. Are you looking in the active or passive node? Which user are you logged
on as in enterprise manager , is it an admin account?
2. Check the APP and SYS logs for any MSDTC errors
Fany Vargas
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
The MSDTC group and resources are all online from Cluster Administrator. If
check SQL Server Support Service it show the service as stopped. The Server
services shows the MSDTC to off.
Please help me with these results.
1. Are you looking in the active or passive node? Which user are you logged
on as in enterprise manager , is it an admin account?
2. Check the APP and SYS logs for any MSDTC errors
Fany Vargas
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 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 Cannot Create Dependencies
Using MS-Article Q301600 I was able to create MSDTC group on a Windows 2003
server with SQL Server 2000 Cluster.
Next step is trying to add resources to the MSDTC group. I tried to add IP
Address, Network Name, or Physical disk to the dependeny list. Everytime I
get to dependency list it is empty.
Please help me add the dependencies to the MSDTC group.
Thanks,
Are the resources you are trying to add in the dependencies in a different
cluster group? You can only add resources to your dependency list if these
resources are in the SAME cluster group.
Fany Vargas
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
server with SQL Server 2000 Cluster.
Next step is trying to add resources to the MSDTC group. I tried to add IP
Address, Network Name, or Physical disk to the dependeny list. Everytime I
get to dependency list it is empty.
Please help me add the dependencies to the MSDTC group.
Thanks,
Are the resources you are trying to add in the dependencies in a different
cluster group? You can only add resources to your dependency list if these
resources are in the SAME cluster group.
Fany Vargas
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
Monday, February 20, 2012
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.
>
>
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.
>
>
MSDTC - running but not available - RPC error?
Hi there.
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:
> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support
I am having problems with MSDTC on a 2-node clustered server. I currently
have it added as a resource in a group with disk storage, SQL Server, an IP
Address and a Network name. When I look at the status of MSDTC using MSSQL
Enterprise Manager on either node, it seems to be running Ok (after I select
"bring online" in cluster admin).
I have a non-clustered SQL Server from which I'd like to call stored
procedures on my clustered server (hence I need MSDTC running). However, on
running these queries, I am seeing problems like this:
select * from CLUSTER.MyDB.dbo.MyTable --this works fine BUT
BEGIN DISTRIBUTED TRANSACTION
select * from CLUSTER.MyDB.dbo.MyTable
COMMIT TRANSACTION
returns errors like
'MSDTC on server unavailable' and my stored procedure calls return errors
like:
'OLE DB error trace - ITransactionJoin::JoinTransaction returned 0x8004d00a'
I have performed some configuration according to
http://support.microsoft.com/kb/817064
and
http://support.microsoft.com/kb/301600
but to no avail.
Any ideas? We tried using DTCPing to obtain more detailed errors and what we
saw were 'RPC' errors (the cluster was unable to ping the other linked server)
Any help would be appreciated!
P.S: A constraint I have is that I can't assign a new IPAddress for MSDTC...
|||Hello,
Is your MSDTC the one from Windows 2003?
/Patrice
|||Yes - it's 2003 - sorry for leaving this out (I've ust gone a bit dizzy from
trying to fix this!)
"Patrice" wrote:
> Hello,
> Is your MSDTC the one from Windows 2003?
> /Patrice
>
|||Hello,
Is it possible for you to do the following test...
Cound you call your SP after
(a) you bring SQL online only after MSDTC was fully up and running
(b) you (try to) bring SQL online before MSDTC was fully up and
running
It would be interesting to notice that everything is fine with (a), and
that you got an "MSDTC on server unavailable" error message with (b).
If it is the case it will mean that you are experiencing the same
problem than the one I experienced a couple of months ago ;-)
/Patrice
|||Hello "Len",
Are you able to do the test I have proposed? Should I continue to
monitor this topic?
Thanks in advance for your reply.
/Patrice
|||If Patrice's test works you should contact Microsoft Product Support and
request the hotfix associated with this KB article:
883955 Availability of Windows Server 2003 COM 1.5 Rollup Package 3
http://support.microsoft.com/?id=883955
Dave Whitney
SQL Support
MSDTC - Give it a dedicated group or use Cluster Group?
Hello group,
I have been testing out SQL 2005 clusters. I noticed that putting the
"Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
its own cluster resource group or in the default Cluster Group with
the quorum works. The latter would be my preference because it saves
an IP address and a disk.
Which way -- dedicated group or shared cluster group -- is the
generally accepted best practice, though?
Thank you in advance,
J Wolfgang Goerlich
Related Links:
Microsoft Article 301600, How to configure Microsoft Distributed
Transaction Coordinator on a Windows Server 2003 cluster
http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
The only reason to give it its own group is performance.
If you have a high load/use for MSDTC, you should configure it in its own
group, however this will impact available drive letters, as the dedicated
group needs a disk (and IP and net-name). If you decide to give MSDTC its
own group, you must carefully design the rest of your cluster in regards to
the available drive letters.
Most applications do not have a high load on MSDTC, and therefore there is
not need for a seperate group. It is very common to place the MSDTC resource
in the Cluster Group, using the Quorum disk.
rgds,
Edwin.
<jwgoerlich@.gmail.com> wrote in message
news:1173815091.825202.19210@.j27g2000cwj.googlegro ups.com...
> Hello group,
> I have been testing out SQL 2005 clusters. I noticed that putting the
> "Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
> its own cluster resource group or in the default Cluster Group with
> the quorum works. The latter would be my preference because it saves
> an IP address and a disk.
> Which way -- dedicated group or shared cluster group -- is the
> generally accepted best practice, though?
> Thank you in advance,
> J Wolfgang Goerlich
>
> Related Links:
> Microsoft Article 301600, How to configure Microsoft Distributed
> Transaction Coordinator on a Windows Server 2003 cluster
> http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
>
|||Much obliged. What's a good rule of thumb to determine a high load?
Tens of transactions per second? Hundreds or more tps?
On Mar 14, 4:54 am, "Edwin vMierlo"
<EdwinvMie...@.discussions.microsoft.com> wrote:
> The only reason to give it its own group is performance.
> If you have a high load/use for MSDTC, you should configure it in its own
> group, however this will impact available drive letters, as the dedicated
> group needs a disk (and IP and net-name). If you decide to give MSDTC its
> own group, you must carefully design the rest of your cluster in regards to
> the available drive letters.
> Most applications do not have a high load on MSDTC, and therefore there is
> not need for a seperate group. It is very common to place the MSDTC resource
> in the Cluster Group, using the Quorum disk.
> rgds,
> Edwin.
|||A simple test:
Put MSDTC in the quorum group. Establish a distributed transaction with SQL
Server, even with itself using a linked server to itself. Now move the
quorum group to passive node. Try to establish another distributed
transaction.
The result is that you cannot. The reason is that when the quorum goes
offline, the SQL Server DTC handle is destroyed.
The only way to alleviate this is to give the DTC its own dedicated cluster
group.
If you only plan on running a single instance of SQL Server, and this is the
only service you will be establishing distributed transactions with, then
put the MS DTC resource inside the SQL Server group, not the quorum.
The Microsoft articles have been updated to reflect this recommendation.
Sincerely,
Anthony Thomas
<jwgoerlich@.gmail.com> wrote in message
news:1173870206.954497.204520@.e1g2000hsg.googlegro ups.com...[vbcol=seagreen]
> Much obliged. What's a good rule of thumb to determine a high load?
> Tens of transactions per second? Hundreds or more tps?
> On Mar 14, 4:54 am, "Edwin vMierlo"
> <EdwinvMie...@.discussions.microsoft.com> wrote:
own[vbcol=seagreen]
dedicated[vbcol=seagreen]
its[vbcol=seagreen]
to[vbcol=seagreen]
is[vbcol=seagreen]
resource
>
|||Alright, I think I am following your explanation. If the MSDTC is in
the quorum resource group (e.g., the Cluster Group) and that group
goes offline then any DTC transactions will fail.
Now, how would this change if the MSDTC were in its own group (e.g.,
MSDTC Resource)? When the MSDTC Resource goes offline, any
distributed transactions will also fail. I am probably missing
something here. What would this dedicated group gain us, then?
J Wolfgang Goerlich
On Mar 16, 10:39 pm, "Anthony Thomas" <ALTho...@.kc.rr.com> wrote:
> A simple test:
> Put MSDTC in the quorum group. Establish a distributed transaction with SQL
> Server, even with itself using a linked server to itself. Now move the
> quorum group to passive node. Try to establish another distributed
> transaction.
> The result is that you cannot. The reason is that when the quorum goes
> offline, the SQL Server DTC handle is destroyed.
> The only way to alleviate this is to give the DTC its own dedicated cluster
> group.
> If you only plan on running a single instance of SQL Server, and this is the
> only service you will be establishing distributed transactions with, then
> put the MS DTC resource inside the SQL Server group, not the quorum.
> The Microsoft articles have been updated to reflect this recommendation.
> Sincerely,
> Anthony Thomas
I have been testing out SQL 2005 clusters. I noticed that putting the
"Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
its own cluster resource group or in the default Cluster Group with
the quorum works. The latter would be my preference because it saves
an IP address and a disk.
Which way -- dedicated group or shared cluster group -- is the
generally accepted best practice, though?
Thank you in advance,
J Wolfgang Goerlich
Related Links:
Microsoft Article 301600, How to configure Microsoft Distributed
Transaction Coordinator on a Windows Server 2003 cluster
http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
The only reason to give it its own group is performance.
If you have a high load/use for MSDTC, you should configure it in its own
group, however this will impact available drive letters, as the dedicated
group needs a disk (and IP and net-name). If you decide to give MSDTC its
own group, you must carefully design the rest of your cluster in regards to
the available drive letters.
Most applications do not have a high load on MSDTC, and therefore there is
not need for a seperate group. It is very common to place the MSDTC resource
in the Cluster Group, using the Quorum disk.
rgds,
Edwin.
<jwgoerlich@.gmail.com> wrote in message
news:1173815091.825202.19210@.j27g2000cwj.googlegro ups.com...
> Hello group,
> I have been testing out SQL 2005 clusters. I noticed that putting the
> "Distributed Transaction Coordinator" resource (i.e., MSDTC) in either
> its own cluster resource group or in the default Cluster Group with
> the quorum works. The latter would be my preference because it saves
> an IP address and a disk.
> Which way -- dedicated group or shared cluster group -- is the
> generally accepted best practice, though?
> Thank you in advance,
> J Wolfgang Goerlich
>
> Related Links:
> Microsoft Article 301600, How to configure Microsoft Distributed
> Transaction Coordinator on a Windows Server 2003 cluster
> http://support.microsoft.com/default.aspx?scid=kb;en-us;301600
>
|||Much obliged. What's a good rule of thumb to determine a high load?
Tens of transactions per second? Hundreds or more tps?
On Mar 14, 4:54 am, "Edwin vMierlo"
<EdwinvMie...@.discussions.microsoft.com> wrote:
> The only reason to give it its own group is performance.
> If you have a high load/use for MSDTC, you should configure it in its own
> group, however this will impact available drive letters, as the dedicated
> group needs a disk (and IP and net-name). If you decide to give MSDTC its
> own group, you must carefully design the rest of your cluster in regards to
> the available drive letters.
> Most applications do not have a high load on MSDTC, and therefore there is
> not need for a seperate group. It is very common to place the MSDTC resource
> in the Cluster Group, using the Quorum disk.
> rgds,
> Edwin.
|||A simple test:
Put MSDTC in the quorum group. Establish a distributed transaction with SQL
Server, even with itself using a linked server to itself. Now move the
quorum group to passive node. Try to establish another distributed
transaction.
The result is that you cannot. The reason is that when the quorum goes
offline, the SQL Server DTC handle is destroyed.
The only way to alleviate this is to give the DTC its own dedicated cluster
group.
If you only plan on running a single instance of SQL Server, and this is the
only service you will be establishing distributed transactions with, then
put the MS DTC resource inside the SQL Server group, not the quorum.
The Microsoft articles have been updated to reflect this recommendation.
Sincerely,
Anthony Thomas
<jwgoerlich@.gmail.com> wrote in message
news:1173870206.954497.204520@.e1g2000hsg.googlegro ups.com...[vbcol=seagreen]
> Much obliged. What's a good rule of thumb to determine a high load?
> Tens of transactions per second? Hundreds or more tps?
> On Mar 14, 4:54 am, "Edwin vMierlo"
> <EdwinvMie...@.discussions.microsoft.com> wrote:
own[vbcol=seagreen]
dedicated[vbcol=seagreen]
its[vbcol=seagreen]
to[vbcol=seagreen]
is[vbcol=seagreen]
resource
>
|||Alright, I think I am following your explanation. If the MSDTC is in
the quorum resource group (e.g., the Cluster Group) and that group
goes offline then any DTC transactions will fail.
Now, how would this change if the MSDTC were in its own group (e.g.,
MSDTC Resource)? When the MSDTC Resource goes offline, any
distributed transactions will also fail. I am probably missing
something here. What would this dedicated group gain us, then?
J Wolfgang Goerlich
On Mar 16, 10:39 pm, "Anthony Thomas" <ALTho...@.kc.rr.com> wrote:
> A simple test:
> Put MSDTC in the quorum group. Establish a distributed transaction with SQL
> Server, even with itself using a linked server to itself. Now move the
> quorum group to passive node. Try to establish another distributed
> transaction.
> The result is that you cannot. The reason is that when the quorum goes
> offline, the SQL Server DTC handle is destroyed.
> The only way to alleviate this is to give the DTC its own dedicated cluster
> group.
> If you only plan on running a single instance of SQL Server, and this is the
> only service you will be establishing distributed transactions with, then
> put the MS DTC resource inside the SQL Server group, not the quorum.
> The Microsoft articles have been updated to reflect this recommendation.
> Sincerely,
> Anthony Thomas
Subscribe to:
Posts (Atom)