3.6.0 Matrix Server Release Notes (5697-7087, February 2008)

PolyServe Matrix Server Release Notes 31

18858 Failed 32-bit upgrade reported as succeeding

When an attempt is made to install a 32-bit version of SQL

Server 2005 SP1 on a 64-bit instance, the installer can incorrectly

report that the installation was successful. Review the SQL

Server setup log to confirm that all components are upgraded

successfully.

18930 SQL Server 2000 instance does not respond to queries when

Instance Aliasing is configured

This issue occurs only when both SQL Server 2000 and 2005

instances are configured in Instance Aliasing and the SQL

Server 2005 instance is configured to listen on any port. When

the SQL Server 2000 instance starts, it attempts to listen on port

1433. However, if the 2005 instance started first, Instance

Aliasing may have already taken port 1433 for that instance. The

SQL Server 2000 instance will then fail to listen on any port.

Workaround. Take one of these actions:

• Restart the SQL Server 2000 instance. It will then take

another port.

• Set the SQL Server 2005 instance to a specific IP address so

that it will not need to listen to a port.

19082 Error 17187 is logged for a SQL Server 2005 instance

When a SQL Server 2005 instance is under heavy load, the

following error may be logged:

Error: 17187, Severity: 16, State: 1.

SQL Server is not ready to accept new client connections;

the connection has been closed. Wait a few minutes before

trying again. If you have access to the error log, look for

the informational message that indicates that SQL Server is

ready before trying to connect again.

This is a known Microsoft SQL Server issue. It has been fixed in

SQL Server 2005 Service Pack 2.

Bug

Description