![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
John, Any ideas how I could fix this without having to rebuild the cluster. I will like to get this resolved but not sure how to tackle it. "John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message news:OWyV8JNsKHA.5036 (AT) TK2MSFTNGP02 (DOT) phx.gbl... That will certainly prevent the group containing that resource from failing over to your NY-SQL2 node. "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:eD8SKPLsKHA.3536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So basically this is what I notice. I have a resource type called SQL Server (Altiris) and when looking at the under possible owners I only see one node and not the second node called NY-SQL2, I only see NY-SQL2. All other types have both nodes as owners. |
#12
| |||
| |||
|
|
It sounds like the SQL instance is not installed to the NY-SQL2 node. Check for local binaries on that node. If so, add the node to the possible owners list and try a "move group". Be prepared to fail it back if necessary. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:O0K5dp%23sKHA.4220 (AT) TK2MSFTNGP05 (DOT) phx.gbl... John, Any ideas how I could fix this without having to rebuild the cluster. I will like to get this resolved but not sure how to tackle it. "John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message news:OWyV8JNsKHA.5036 (AT) TK2MSFTNGP02 (DOT) phx.gbl... That will certainly prevent the group containing that resource from failing over to your NY-SQL2 node. "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:eD8SKPLsKHA.3536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So basically this is what I notice. I have a resource type called SQL Server (Altiris) and when looking at the under possible owners I only see one node and not the second node called NY-SQL2, I only see NY-SQL2. All other types have both nodes as owners. |
#13
| |||
| |||
|
|
So install the default instance on the server, I just looked in add/remove and clicked on MS SQL server 2005 and there is nothing under SQL server 2005 Instance. There is no instance in the secondary node. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:uD8BS6$sKHA.1608 (AT) TK2MSFTNGP05 (DOT) phx.gbl... It sounds like the SQL instance is not installed to the NY-SQL2 node. Check for local binaries on that node. If so, add the node to the possible owners list and try a "move group". Be prepared to fail it back if necessary. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:O0K5dp%23sKHA.4220 (AT) TK2MSFTNGP05 (DOT) phx.gbl... John, Any ideas how I could fix this without having to rebuild the cluster. I will like to get this resolved but not sure how to tackle it. "John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message news:OWyV8JNsKHA.5036 (AT) TK2MSFTNGP02 (DOT) phx.gbl... That will certainly prevent the group containing that resource from failing over to your NY-SQL2 node. "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:eD8SKPLsKHA.3536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So basically this is what I notice. I have a resource type called SQL Server (Altiris) and when looking at the under possible owners I only see one node and not the second node called NY-SQL2, I only see NY-SQL2. All other types have both nodes as owners. |
#14
| |||
| |||
|
|
I think we have found the problem. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:urJU0mAtKHA.4568 (AT) TK2MSFTNGP05 (DOT) phx.gbl... So install the default instance on the server, I just looked in add/remove and clicked on MS SQL server 2005 and there is nothing under SQL server 2005 Instance. There is no instance in the secondary node. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:uD8BS6$sKHA.1608 (AT) TK2MSFTNGP05 (DOT) phx.gbl... It sounds like the SQL instance is not installed to the NY-SQL2 node. Check for local binaries on that node. If so, add the node to the possible owners list and try a "move group". Be prepared to fail it back if necessary. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:O0K5dp%23sKHA.4220 (AT) TK2MSFTNGP05 (DOT) phx.gbl... John, Any ideas how I could fix this without having to rebuild the cluster. I will like to get this resolved but not sure how to tackle it. "John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message news:OWyV8JNsKHA.5036 (AT) TK2MSFTNGP02 (DOT) phx.gbl... That will certainly prevent the group containing that resource from failing over to your NY-SQL2 node. "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:eD8SKPLsKHA.3536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So basically this is what I notice. I have a resource type called SQL Server (Altiris) and when looking at the under possible owners I only see one node and not the second node called NY-SQL2, I only see NY-SQL2. All other types have both nodes as owners. |
#15
| |||
| |||
|
|
so just reinstall sql on the second node and make sure the instance is installed? "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:elL5jTDtKHA.1608 (AT) TK2MSFTNGP05 (DOT) phx.gbl... I think we have found the problem. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:urJU0mAtKHA.4568 (AT) TK2MSFTNGP05 (DOT) phx.gbl... So install the default instance on the server, I just looked in add/remove and clicked on MS SQL server 2005 and there is nothing under SQL server 2005 Instance. There is no instance in the secondary node. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:uD8BS6$sKHA.1608 (AT) TK2MSFTNGP05 (DOT) phx.gbl... It sounds like the SQL instance is not installed to the NY-SQL2 node. Check for local binaries on that node. If so, add the node to the possible owners list and try a "move group". Be prepared to fail it back if necessary. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:O0K5dp%23sKHA.4220 (AT) TK2MSFTNGP05 (DOT) phx.gbl... John, Any ideas how I could fix this without having to rebuild the cluster. I will like to get this resolved but not sure how to tackle it. "John Toner [MVP]" <jtoner (AT) DIE (DOT) SPAM.DIE.mvps.org> wrote in message news:OWyV8JNsKHA.5036 (AT) TK2MSFTNGP02 (DOT) phx.gbl... That will certainly prevent the group containing that resource from failing over to your NY-SQL2 node. "Amador" <amador (AT) agconsulting (DOT) info> wrote in message news:eD8SKPLsKHA.3536 (AT) TK2MSFTNGP06 (DOT) phx.gbl... So basically this is what I notice. I have a resource type called SQL Server (Altiris) and when looking at the under possible owners I only see one node and not the second node called NY-SQL2, I only see NY-SQL2. All other types have both nodes as owners. |
![]() |
| Thread Tools | |
| Display Modes | |
| |