 | |
Re: SQL2K setup fails on 2K3 Cluster...Can't create Virtual Srvr resou
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| ||||||
| ||||||
|
Re: SQL2K setup fails on 2K3 Cluster...Can't create Virtual Srvr resou -
06-22-2004
, 11:20 AM
|
Help! Installing SQL 2000 Ent. Ed. on a Windows Server 2003, 2 node cluster. I have clustering installed and configured on both machines and can |
've installed the MSDTC service and added it as a resource with its
recommended resource dependencies. As far as I can tell at this point, my
cluster is ready.....
Quote:
|
Installing SQL 2000 onto cluster: I launch SQL2K Setup and after getting the initial error warning about running SQL Server SP2 or later on this |
configuring remote nodes. The installation begins on node 2, the warning is
displayed again, and then it continues until an error is generated that
says:
Quote:
|
"An error occurred while creating virtual server resources for clustering. The specified module could not be found." What the heck is this talking |
Quote:
|
More interesting nuggets: I think my cluster is bogus, and why SQL won't install. After setting up clustering on both nodes, I was able to access the |
I try Cluster Admin. by connecting to the virtual server, using either the
FQDN or IP address, I get an "Access Denied" message dialog, and C.A. wont'
launch. I also see an "Access Denied" in the SQLSTP.LOG for the SQL Server
installation on to the cluster, but I can't determine what it's related to.
I have a feeling this has something to do with my failed SQL setup, but I
can't pin it down.
Quote:
|
I've had absolutely the hardest time setting up this cluster that I'm thinking of going back to Win2K server. It was much more strait-forward, and |
Quote:
|
Please Help! If anyone knows what is causing this error to occur, or if I need to start over, please help if you can. Thank you very much in advance. Thanks! |
#2
| |||
| |||
|
|
Hi Geoff, Thanks for responding to my plea. I will try your suggestion, but I'm going to leave this thread open to see what other ideas come through. I have |
you mentioned. That I will do. All 3 of the accounts you mention are in use
and all are members of the local admin groups for each node, so I should be
good there.
Quote:
|
As for DNS, the cluster VIP and name did get registered in the DNS table. Also, both nodes' names and IPs are registering as well. Question: I've read where Terminal Services can cause issues. I have Remote Desktop enabled for remote admin, is this the same as having T.S. |
Quote:
|
Thanks again. "Geoff N. Hiten" wrote: First, you seem to be on the right track with the problem. If you cannot access your cluster via the cluster name or IP address, then something is badly wrong. Make sure all accounts involved are local administrator accounts on the cluster nodes. That includes the cluster service account, the SQL serice account(s), and the installation account (the one you are logged in with when you launch the install.) All accounts must be domain-level accounts as well. Finally, log into the console of each node manually using each account so that the local structures get set correctly for the account profile. One more thing. Make sure the host nodes have a correct DNS setup and register themselves and the new cluster correctly in DNS. Since you cannot connect via IP, I don't think this is the problem, but it won't hurt to check. I have found Win2003 clustering to be far easier than W2000 clustering, but that may just be me. -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Fonkberry" <Fonkberry (AT) discussions (DOT) microsoft.com> wrote in message news  E7A43FA-822A-447A-B802-E9F8D2541D07 (AT) microsoft (DOT) com...Help! Installing SQL 2000 Ent. Ed. on a Windows Server 2003, 2 node cluster. I have clustering installed and configured on both machines and can failover resources between the two servers all day long. No problem there. I 've installed the MSDTC service and added it as a resource with its recommended resource dependencies. As far as I can tell at this point, my cluster is ready..... Installing SQL 2000 onto cluster: I launch SQL2K Setup and after getting the initial error warning about running SQL Server SP2 or later on this version of Windows ('03), the installation reaches the part where it begins configuring remote nodes. The installation begins on node 2, the warning is displayed again, and then it continues until an error is generated that says: "An error occurred while creating virtual server resources for clustering. The specified module could not be found." What the heck is this talking about?! More interesting nuggets: I think my cluster is bogus, and why SQL won't install. After setting up clustering on both nodes, I was able to access the cluster in Cluster Administrator only by using the local (.) login. Whenever I try Cluster Admin. by connecting to the virtual server, using either the FQDN or IP address, I get an "Access Denied" message dialog, and C.A. wont' launch. I also see an "Access Denied" in the SQLSTP.LOG for the SQL Server installation on to the cluster, but I can't determine what it's related to. I have a feeling this has something to do with my failed SQL setup, but I can't pin it down. I've had absolutely the hardest time setting up this cluster that I'm thinking of going back to Win2K server. It was much more strait-forward, and actually worked! Please Help! If anyone knows what is causing this error to occur, or if I need to start over, please help if you can. Thank you very much in advance. Thanks! |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.