4.1.0 HP Polyserve Matrix Server Release Notes (T5392-96068, October 2010)

DescriptionNumber
Confusing error message appears when attempting to virtualize a SQL instance with an unsupported
service account
When an attempt is made to virtualize a SQL instance using the local Administrator account as
the service account, the following operating system error appears:
A member could not be added to or removed from the local group
because the member does not exist
HP PolyServe Software for Microsoft SQL Server does not support using local user service accounts
for the service account. Instead, use a domain user service account or LocalSystem.
18814
Warning that AdminConnection\TCP protocol is not valid
When a SQL 2005 instance is installed and the value of the TcpDynamicPorts key is set to 0, the
following Application event is written repeatedly for the instance:
The configuration of the AdminConnection\TCP Protocol in the
SQL instance <instance> is not valid.
This warning can be ignored. When SQL Server starts, it will set the key. The registry key can be
found at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<MSSQL.x>\\
MSSQLServer\SuperSocketNetLib\ AdminConnection
18857
Failed 32-bit upgrade reported as succeeding
When an attempt is made to install a 32-bit version of SQL Server 2005 SP1 on a 64-bit instance,
the installer can incorrectly report that the installation was successful. Review the SQL Server setup
log to confirm that all components are upgraded successfully.
18858
Multi-Node Installer does not prompt for authentication credentials
In some situations, the Multi-Node Installer does not prompt for the authentication credentials
needed to access certain nodes and instead does not list those nodes as being available for the
installation. This situation can occur if nodes are in different domains, or if the account used to
logon to the Installer is not authorized to manage all of the nodes.
Workaround. Logon using an account belonging to a role that is authorized to manage all nodes
that should be included in the installation.
19334
PolyServe SQL Browser Service does not start after uninstall/reinstall
If HP PolyServe Software for Microsoft SQL Server is uninstalled and then reinstalled, the PolyServe
SQL Browser Service will not start. This issue occurs because both the PolyServe SQL Browser
Service and the Microsoft SQL Browser Service are enabled after the reinstall, which prevents the
PolyServe SQL Browser Service from starting.
Workaround. Open the SQL Instance Aliasing window and click Advanced. If “Enable the PolyServe
SQL Browser Service” is already checked on the Advanced Setting dialog, uncheck it and click
OK, and then click Apply on the SQL Instance Aliasing window. Now reopen the SQL Instance
Aliasing window and repeat this step, this time checking Enable the PolyServe SQL Browser Service.
The Microsoft SQL Browser Service will now be disabled, allowing the PolyServe SQL Browser
Service to start.
19401
18