3.6.1 HP PolyServe Software for Microsoft SQL Server Release Notes (T5392-96026, August 2008)

• Defect 16256. The Applications tab did not indicate whether MS DTC was
enabled on a Virtual SQL Ser ver.
• D efect 16308. The installer did not verify that a virtualized SQL instance was in
maintain mode before installing a ser vice pack or hotfix.
• Defect 16370. The -–operational and --maintenance flags provided
with the mx vsql status command did not work.
• Defect 16571. A log message from the Multi-Node Installer caused Matrix Server
to fail when the log was viewed through the Matrix Server "View Log" command.
• Defect 1 8012. The PolyServe Managem ent Console dialogs used to configure
Instance Aliasing did not validate instance and server names.
• Defect 18081. A Virtual SQL instance did not start and a probe error reported
that the instance was already running.
• D efect 18823. When the Instance Aliasing file contained an invalid record, the
error m essage that was generated did not include the invalid record.
• Defect 18834. When multiple ports were assigned to a SQL instance, Instance
Aliasing did n ot construct the browser string corre ctly.
• Defect 19103. Instance Aliasing did not prevent the creation of duplicate legacy
IP addresses associated with different “real” IP addresses.
• Defect 19194 . The Multi-Node Installer did not sor t the list servers ava ilable
for an installation.
• Defect 19196. When the autostart option was selected for Analysis Servic es
or Reporting Services in the Multi-Node Installer, the corresponding account
was not automatically selected.
• Defect 19211. The Multi-N o d e Installer did not support NTLM authentication.
• Defect 1 9250. After a Virtual SQL Server was failed over to another nod e,
alerts remained on the original node.
• Defect 19331. When a duplicate record was entered into the ia.conf file,
Instance Aliasing did not discard the duplicate.
• Defect 19529. The message associated with Event 40161 did n ot report that
Registry Replicator failed to start replication of the keys.
• Defect 19544. The mx vsq update command could replace the application
name with the IP address fo r the Vir tual SQL Server.
• Defect 19545. When multiple SQL instances were assigned to the same Virtual
SQL Server, the Multi-Node Upgrade wizard incorrectly warned that the SQL
instances were included in multiple Virtual SQL Servers.
• Defect 19612. When Instance Aliasing was started on a node, it did not remove
any legacy IPs that were bound to the node.
• Defect 19627. Theusernameordomainspecified for a SQL Ser ver installation
or upgradecould notcontain aperiod.
• Defect 19803. The registry was not updated when a Virtual SQL instance was
upgrad ed.
• Defect 19830. After a SQL 20 05 instance was virtualized, the @@servername
property returned the physical server name.
4