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

DescriptionNumber
Instance does not start when the same port is used for IA and legacy mappings
When the same port is used to map a legacy IP address to the IP address for a Virtual SQL Server,
the SQL instance will be unable to start while the legacy mapping is active with the same port.
This can prevent SQL from starting during Virtual SQL Server failovers and during a machine
reboot.
22374
IA service generates log messages after upgrade
After an upgrade to the 4.0 release, messages such as the following appear in the log file:
IA service: Event was signalled, might need to exit
Workaround. The Service Control Manager is raising an event to the IA service. Reboot the node
to clear the event.
22571
SQL/SSAS 2008 instances can be virtualized with SQL 2005 data
When virtualizing a SQL Server or Analysis Services instance, HP PolyServe Software does not
verify that the instance version matches the version of the data specified as the virtual dataroot.
Consequently, a SQL or SSAS 2008 instance can be virtualized with a SQL 2005 dataroot. It is
important that the existing data is correct for the instance that is being virtualized. When you
specify the virtual dataroot for a SQL/SSAS 2008 instance, be sure that the location does not
contain data for a SQL/SSAS 2005 instance.
27688
Multi-Node Upgrade Wizard does not prompt to reboot after Service Pack and hotfix installations
Certain SQL Server service packs and hotfixes require that the node be rebooted after the upgrade;
however, the Multi-Node Upgrade Wizard does not prompt you to reboot. It is critical that nodes
are rebooted appropriately after upgrades. See the Microsoft documentation for your service
pack/hotfix to determine whether it requires a reboot.
27714
Reinstallation of SQL Server 2005 instance fails with error 1603
When an attempt is made to reinstall a SQL Server 2005 instance, the installation may fail with
this error because the previous uninstall of the instance did not completely remove all registry keys
and related folders for the instance.
Workaround. Use Add or Remove Programs to delete the “stale entry” SQL instance and then
reinstall it. See the following article for more information:
http://blogs.msdn.com/sqlserverfaq/archive/2009/02/11/
sql-server-2005-instance-failing-to-install-after-trying-to-reinstall-with-error-1603.aspx
27772
MSDTC service fails when the operating system is installed from a ghost image
When a ghost image is used to install the operating system on the cluster nodes, the MSDTC service
on one node does not coordinate with DTC on the other nodes. This situation occurs because
MSDTC is a Windows component and has the same connection ID on each node, causing an RPC
failure.
Workaround. Uninstall and reinstall the MSDTC service as described in your Microsoft
documentation. You can then virtualize the MSDTC service.
27807
20