3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 7: Troubleshooting 105

Cannot Access a Virtual SQL Instance

from the Active Node

To successfully access a Virtual SQL instance on the active node, the

following requirements must be met:

• An alias must exist to direct the Virtual SQL instance. MxDB for SQL

Server creates this instance. To verify that the alias exists for a SQL

Server 2005 instance, use Configuration Manager > Alias. For a SQL

Server 2000 instance, Use the Client Network Utility and open the

Alias tab.

• The instance must be listening on TCP. Check the SQL log to verify

this.

• Forward and reverse lookup works for the instance. See “DNS

Requirement for Virtual SQL Servers” on page 54 for more

information.

• The instance is registered correctly in Active Directory. Check for a

valid SPN.

SQL Server 2005 Instance Does Not Start

If the computer name for a node has ever been changed, the SQL 2005

instances installed on that node may not start in the following

circumstances:

• During virtualization

• During failover

• After upgrading to a later version of MxDB for SQL Server

To work around this issue, change the service account group names to

match the current name of the node. Next, remove the node from the

domain and then rejoin it. The SQL Server 2005 instances will now start

properly.