I have 2-node SQL Server 2005 Cluster which configured as
Active/Passive mode, let say A node and P node. I already install 1 CRM
instance on this cluster before. Now I wanna to install a second 2-node
cluster on these 2 servers, this time, A node will act as the passive
node of 2nd cluster, P node will act as the active node. So I have to
install them under named instance. After sql server installation, i
patched SP3.
now the environment is below (All running 64-bit platform, OS is Windows Server 2008 x64, SP1):
Cluster 1 CRMSQLVS01 (192.168.10.101)
Active Node: A (192.168.10.1)
Passive Node: B (192.168.10.2)
Instance name: MSSQL (Default Instance)
Cluster 2 CRMSQLVS02 (192.168.10.102)
Active Node: B (192.168.10.2)
Passive Node: A (192.168.10.1)
Instance name CRMSQL2 (Named Instance)
All services are running fine. So I start install another instance on Cluster 2. On Server Server page, I type 'CRMSQLVS02\CRMSQL2', finally it gave me a error message: 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)', i read some posts which searched via search engine,
http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-
interfaces-error-26-error-locating-server-instance-specified.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/02/27/unable-to-connect
-to-a-sql-server-named-instance-on-a-cluster.aspx
I use portqry.exe -n yourservername -p UDP -e 1434 to check UDP connection, both worked on each server's physical ip, but failed on cluster virtual server ip.
Finally, i found a workaround on MS Forum.
http://social.microsoft.com/forums/en-US/crmdeployment/thread/30bd
2f37-27a5-4598-8183-d5780e05b1e4/
create the following key in the registry:
now the environment is below (All running 64-bit platform, OS is Windows Server 2008 x64, SP1):
Cluster 1 CRMSQLVS01 (192.168.10.101)
Active Node: A (192.168.10.1)
Passive Node: B (192.168.10.2)
Instance name: MSSQL (Default Instance)
Cluster 2 CRMSQLVS02 (192.168.10.102)
Active Node: B (192.168.10.2)
Passive Node: A (192.168.10.1)
Instance name CRMSQL2 (Named Instance)
All services are running fine. So I start install another instance on Cluster 2. On Server Server page, I type 'CRMSQLVS02\CRMSQL2', finally it gave me a error message: 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)', i read some posts which searched via search engine,
http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-
interfaces-error-26-error-locating-server-instance-specified.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/02/27/unable-to-connect
-to-a-sql-server-named-instance-on-a-cluster.aspx
I use portqry.exe -n yourservername -p UDP -e 1434 to check UDP connection, both worked on each server's physical ip, but failed on cluster virtual server ip.
Finally, i found a workaround on MS Forum.
http://social.microsoft.com/forums/en-US/crmdeployment/thread/30bd
2f37-27a5-4598-8183-d5780e05b1e4/
create the following key in the registry:
in HKLM\Software\Microsoft\MSSQLServer\Client\ConnectTo
Create the following:
Name : <SQLServerName>\<SQLServerInstanceName>
Type : REG_SZ
Value: DBMSSOCN,<SQLServerName>\<SQLServerInstanceName>,
<PortNumber>
Create the following:
Name : <SQLServerName>\<SQLServerInstanceName>
Type : REG_SZ
Value: DBMSSOCN,<SQLServerName>\<SQLServerInstanceName>,
<PortNumber>
Leave a comment