4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

To correct this problem, you will need to set the service account for the instance to
either a domain user or LocalSystem on all nodes. When using SQL Server
Configuration Manager to change the user for the service account, be sure to type
the new user name using NTLM-style credentials (DOMAIN\user). You can also
browse for the appropriate user account.
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. 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 Servers on page 73, 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:
HP PolyServe Software for Microsoft SQL Server 4.1 administration guide 141