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

DescriptionNumber
mx quota unsetuser command does not work
When the mx quota unsetuser command is issued, the command does not remove quota
entries.
28194
HP PolyServe Software for Microsoft SQL Server
The following considerations affect HP PolyServe Software for Microsoft SQL Server.
DescriptionNumber
Virtual SQL Server names are not checked against existing NetBIOS names
When a Virtual SQL Server is created, its name is not checked against the existing NetBIOS names.
Consequently, it is possible to create duplicate NetBIOS names on the network. This will cause the
Virtual SQL Server to fail when it is started.
Workaround. When you create a Virtual SQL Server, ensure that the name is not already assigned
on the network. A DNS lookup is performed when the name is entered, but you should also manually
ping the name to ensure that it is not being used.
3737
Virtual SQL Server backup instances may appear in Enterprise Manager
When the Instance Aliasing feature is not used, HP PolyServe Software for Microsoft SQL Server
does not keep the backup instances from appearing in the SQL Server Enterprise Manager. These
backup SQL Server instances are not active and should not be selected for operations. Be sure to
select the active SQL Server instance from within Enterprise Manager.
4046
PolyServe Management Console shows inconsistent information
The list of available servers on the Add Virtual SQL Server window may identify some servers by
their DNS names and other servers by their IP addresses. This occurs because either reverse lookup
is not set up or it is still resolving the names.
4432
Error can occur if timeouts exceeded
Under a controlled failover scenario (for example, disabling an instance via the PolyServe
Management Console), the system will allow 45 seconds for SQL Server and SQL Agent to stop.
If it takes longer than the allocated time to stop these services, an Alert will appear on the
Management Console.
4846
Windows limitation for nodes with 16 instances of SQL Server
If the SQL Server service startup account is a NT domain user and the node needs to start 16
instances of SQL Server, it will run out of available desktops.
Workaround. Reduce the third SharedSection value from 512 to 256. See the following Knowledge
Base article for details:
http://support.microsoft.com/?id=184802
If the SQL Server service startup account is LocalSystem, this bug and the workaround do not apply.
5288
Port information is not updated on the Management Console
When the TCP port used by a SQL service monitor is changed manually, the PolyServe Management
Console does not display the new port number.
5291
14