3.4.3 MxDB for SQL Server Release Notes

Table Of Contents

Matrix DataBase Solution Pack for SQL Server™ Release Notes 4

• Defect 14549. Installations of SQL Server 2005 SP1 failed because of a

security error in the registry.

• Defect 14558, 14586. When DNS was not configured properly, the SQL

agent and SQL clients could not connect to a Virtual SQL Server. See

the section “DNS Misconfiguration Causes Virtual SQL Server

Connection to Fail” in Chapter 4 of the MxDB for SQL Server

Installation and Administration Guide for information about configuring

DNS.

• Defect 14559. A SQL Server instance would not start because there

were duplicate IP entries in the registry.

• Defect 14573. A SQL Server instance could not be removed after the

associated Virtual SQL Server was rehosted.

• Defect 14585. When the SQL Server service account for an instance

was a domain user account with limited access (i.e., non-local admin),

the associated Virtual SQL Server could not be failed over to a backup

node.

• Defect 14852. A 64-bit SQL instance could not be virtualized on a 32-

bit node.

• Defect 14860. Re-hosting an instance between a 32-bit and 64-bit server

migrated an incorrect configuration that prevented the 64-bit server

from starting the services.

• Defect 14871. A SQL Server 2005 instance with SP1 could not be

uninstalled after it was virtualized.

• Defect 14896. A duplicate IP address in the configuration prevented

the start of SQL virtualization.

• Defect 14904. SQL virtualization did not start when a Virtual SQL

Server was moved from Maintenance to Operational mode because

the registry was not updated.

• Defect 14911. SQL virtualization did not start because the original

vhost registry settings had not been restored.