4.0.0 HP Polyserve Matrix Server Release Notes (T5392-96051, March 2010)

DescriptionIssue
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 the upgrade to HP PolyServe Software for Microsoft SQL Server 3.8
Workaround. 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.
19632
Virtual SQL Server does not start during upgrade
When the servers in a cluster are upgraded in two groups, the Virtual SQL Servers in group A are
failed over to group B while the group A servers are upgraded. The Virtual SQL Servers are then
failed back to group A so that the servers in group B can be upgraded. If MS DTC is enabled on a
Virtual SQL Server, the Virtual SQL Server may not start when it is failed back to group A. In general,
this issue occurs only with Virtual SQL Servers configured with more than four SQL instances.
Workaround. Restart the MS DTC service on the group A node. The Virtual SQL Server will then
start successfully.
19671
SQL Server instance cannot be virtualized when case of service account does not match case of
domain name
When specifying a domain and username for a SQL Server service account, be sure that the case
used for the domain matches the actual case used by the domain name. For example, if the domain
name is PLDAR1, the service account must be specified as PLDAR1\username, not pldar1\username.
If the case does not match, an attempt to virtualize the SQL Server instance will fail.
20835
MS DTC service cannot be virtualized
If WMI components or references are corrupted, an attempt to virtualize the MS DTC service will
fail. The following command reports that the WMI repository is not working:
C:\Documents and Settings\Administrator> gwmi win32_service
-filter "name ='msdtc'"
Get-WmiObject : Invalid class
At line:1 char:5
+ gwmi <<<< win32_service -filter "name = 'msdtc'"
To rebuild the repository, run this command:
rundll32 wbemupgd, RepairWMISetup
When the repository is rebuilt, the MS DTC service can be virtualized.
21083
Instance does not start after Virtual SQL Server is returned to operational mode
This issue occurs when a Virtual SQL Server is put into maintenance mode while it is currently being
rehosted to another node. To prevent this issue, wait until the rehost operation is complete before
placing the Virtual SQL Server into maintenance mode.
21159
Multi-Node Installer can remove instances incorrectly from list of instances to be created
When installing SQL instances, the Define the Instances to Install dialog allows you to sort the list of
instances to be created. If you then use Remove to remove certain instances from the list, the wrong
instances will be deleted.
Workaround. Use Add to add the deleted instances/nodes back to the list and then restore the list
to its default sorting order (the sort icon is not displayed on the header column.) You can then remove
the unneeded instances from the list.
22139
HP PolyServe Matrix Server release notes 19