4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

• An alias must exist to direct the Virtual SQL instance. HP PolyServe Software creates this alias. To
verify that the alias exists for a SQL Server instance, use Configuration Manager > Alias.
• 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 Serv-
ers” on page 57, 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 HP PolyServe Software for Microsoft 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.
Virtualized SSAS instance does not start and reports an invalid
request address
After a SSAS instance is virtualized, the SSAS service does not start and the following error is reported:
The service cannot be started: The following system error occurred:
The request address is not valid in its context.
This error occurs when an attempt is made to start a virtualized named SSAS instance on a primary
node when the default SSAS instance is also installed on that node and has been started natively. By
default, the default instance is configured to listen on 0.0.0.0:2383. An attempt to start another
instance with another IP address, but listening on port 2383, will fail with the above message.
To correct this situation, take one of the following actions:
• Virtualize the default instance before virtualizing any named instances.
• Do not install a default instance on a node where named instances are installed.
Error when creating a distributor for replication
Typically you connect to HP PolyServe Software for Microsoft SQL Server via <virtual name>,<tcp
port>. However, this connection method does not work when configuring a distributor for replication
and results in the following error.
Troubleshooting122