December 11, 2008 at 4:24 am
We have some SQL connectivity issues with a new sql cluster we have had installed (by a 3rd party) and
I cannot connect using the surface area configuration tool (http://msdn.microsoft.com/en-us/library/ms173748.aspx) to troubleshoot. I have had a thorough search of other posts and followed their explanations but I am either getting the virtual server name wrong or there is another issue. I have also followed up on the MOF file referenced for WMI in this post http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx and this was successfully compiled according to the mof log.
Given the information below can someone tell me what the virtual server name should be?
Windows Server 2003 SP2 Enterprise active, active passive cluster with TWO SQL 2005 x64 SP2 Enterprise instances located in the "webDomain". I normally connect to instance 1 using "SW1.WebDomain.local\InstSW1". Both instances are on port 1433.
ClusterName="WebCluster01" (this is the name I connect to with cluster administrator)
Cluster Application groups (seen in cluster administrator once connected to cluster)
Cluster Application group 1 = "SQLWEB1"
Cluster Application group 2 = "SQLWEB2"
SQLWEB1 Resource - IP address = "SW1"
SQLWEB1 Resource - Network Name = "SW1"
SQLWEB1 Resource - SQL Server = "InstSW1"
SQLWEB1 Resource - SQL Server Agent = "InstSW1"
SQLWEB2 Resource - IP address = "SW2"
SQLWEB2 Resource - Network Name = "SW2"
SQLWEB2 Resource - SQL Server = "InstSW2"
SQLWEB2 Resource - SQL Server Agent = "InstSW2"
Node1 name = "WebNode01" (active for instance 1)
Node2 name = "WebNode02" (active for instance 2)
Node3 name = "WebNode03" (passive)
I dont know if this will have an impact but We have had issues with the SQL server names not being present in AD and missing SPN but we think these have now been resolved.
Thanks for your help.
August 28, 2025 at 6:25 am
Thanks bro.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply